Releases: duchess-rs/duchess
v0.3.0
What's Changed
- Update contributor guide. by @bowemi in #167
- Couple of smaller doc fixes by @badboy in #171
- Update thread model to include new understandings by @rcoh in #162
- Add in checks for the type of Java Class/Interface by @ekureina in #168
- Add support for multiple Errors to surface by @ekureina in #170
- Generate JNI fuction following JNI standards by @bowemi in #169
- Update contributor guidelines on how to run a single test by @bowemi in #175
- Java to rust exceptions by @bowemi in #176
- cherry-pick some refactorings by @nikomatsakis in #177
- Add support for returning scalars by @bowemi in #181
- create a duchess-reflect crate by @nikomatsakis in #178
- Allow to specify minimum or maximum JNI versions by @ekureina in #180
- Fix
Option<T>
fields when used as method arguments as well as inToJava
by @rcoh in #182 - update changelog, prepare release by @rcoh in #183
New Contributors
- @bowemi made their first contribution in #167
- @badboy made their first contribution in #171
- @ekureina made their first contribution in #168
Full Changelog: v0.2.1...v0.3.0
v0.2.1 (June 4th 2021)
v0.2.0 (May 20th, 2024)
This release contains several breaking changes to be aware of:
-
The public API has been simplfied: Duchess references are now "global" references by default. The
to_rust
,global
, andexecute
combinators have all been merged. You now invokeexecute
and then the result depends on the return value: returning aJava<T>
will create a global reference (matching the previous behavior ofglobal
), and returning a Rust value likeString
will invoke the "to rust" conversion (liketo_rust
used to do). For context and examples of upgrading see #147. -
Jvm::with
has been removed. You can no longer obtain explicit handles to the JVM, preventing panics due to nestedJvm::with
invocations. For context and examples see #147. -
JvmOp
, the type returned by most Duchess operations-in-progress is now#[must_use]
. If you encounter this error in your code, note that the code as written had no effect.JvmOp
does nothing unless.execute()
is called.
All changes since the previous release
- Improvements to
DUCHESS_DEBUG
and other misc small changes by @rcoh in #131 - add resolver 2 to remove warning by @rcoh in #132
- Coverage testing by @rcoh in #134
- Threat model by @nikomatsakis in #135
- More work on threat model by @nikomatsakis in #136
- Automatically bless tests once a night by @oli-obk in #137
- Automatically publish coverage information to GitHub pages by @rcoh in #139
- Update threat model by @rcoh in #140
- Add tests of errors and hashmaps by @rcoh in #141
- Fix windows by bumping to the latest ui_test version by @oli-obk in #145
- Add additional test coverage by @rcoh in #143
- simplify public API, only allowing global JVM references by @nikomatsakis in #147
- Add
must_use
to JvmOp by @rcoh in #151 - update tests for new rustc version by @rcoh in #152
- Fix method descriptor for
X extends Y
by @rcoh in #150 - Release 0.2.0 by @rcoh in #154
New Contributors
Full Changelog: v0.1.7...v0.2.0