deps: update dependency org.graalvm.buildtools:junit-platform-native to v0.9.6 #330
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.9.5
->0.9.6
Release Notes
graalvm/native-build-tools
v0.9.6
Compare Source
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:
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
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.