0.9.6
Release highlights
This release is another important step towards a stable version. The most important change in this release is the integration with JUnit 5.8 which brings a number of improvements, which is a breaking change for Maven users. Apart from this, for Maven, the biggest change is the ability to run with the native GraalVM agent (to generate reflection files). Gradle users now have the ability to configure multiple test suites.
See below for more details on the changes.
[Gradle and Maven] Upgrade to JUnit 5.8
The plugins now depend on JUnit 5.8 which provides an official test listener which is used by these plugins.
As a consequence, Maven users will have to configure their builds to enable the plugin extensions:
<plugin>
<groupId>org.graalvm.buildtools</groupId>
<artifactId>native-maven-plugin</artifactId>
<version>${native.maven.plugin.version}</version>
<extensions>true</extensions>
...
</plugin>
The dependency on junit-platform-native
which used to be required pre-0.9.6 can now safely be removed.
For Gradle users, there's no impact on the configuration, however a good consequence is that the junit-native-platform
dependency no longer leaks into your application's classpath.
[Maven] Agent support for Maven plugin
The Maven plugin now supports the GraalVM agent to generate configuration files.
Please refer to the Maven Plugin documentation for details.
[Gradle] Disabling testing support
The Gradle plugin now provides an option to disable testing support.
This can be useful if the test framework you are using doesn't work with this plugin or that you simply don't want to execute tests natively.
To disable tests, use the graalvmNative
configuration block:
graalvmNative {
testSupport.set(false)
}
[Gradle] Configuring additional test images
The Gradle plugin now supports building multiple test images, which can be used to execute tests natively for more kinds of tests: integration tests, functional tests, ...
For more information, please refer to the Gradle plugin documentation