deps: update dependency org.graalvm.buildtools:native-maven-plugin to v0.9.8

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.graalvm.buildtools:native-maven-plugin	0.9.5 -> 0.9.8

---

Release Notes

graalvm/native-build-tools

v0.9.8

Compare Source

Release highlights

This release contains various bugfixes and improvements for both the Maven and Gradle plugins.

Gradle plugin

• [Breaking change] The agent option has been replaced with an agent { ... } configuration block which includes an enabled property.
• Toolchain support can now be disabled altogether, which can be useful when using GraalVM Enterprise Edition.
  • See Disabling toolchain detection for details.
• Fixed a bug when using a fat jar which assumed that all entries to be repackaged were jars.
• Agent options are now configurable.
  • Note that the experimental-class-loader-support agent option is no longer added by default.
  • See Configuring agent options for details.
• Added an option to perform resource detection in classpath entries which contain a native-image/resource-config.json file.

Maven plugin

• The agent can now be enabled in the POM.
  • See Enabling the agent for details.
• Agent options are now configurable.
  • Note that the experimental-class-loader-support agent option is no longer added by default.
  • See Configuring agent options for details.
• Added an option to perform resource detection in classpath entries which contain a native-image/resource-config.json file.

JUnit Platform Native

• Builds now correctly fail if a container-level extension or lifecycle method fails --
  for example, if an @BeforeAll method in a JUnit Jupiter test class throws an exception.
• Builds no longer fail when tests are aborted -- for example, via a failed assumption.
• Improved documentation for JUnit Platform and Maven Surefire support in the plugins.

Detailed changes

Please refer to this milestone.

v0.9.7.1

Compare Source

Release highlights

This release is a bugfix release for Maven users. If you were using the plugin on a multi-project build or a build which uses a parent POM we recommend to upgrade.

[Maven] Fix test execution when plugin is declared in a parent POM

The plugin will now work properly if declared in a parent pom.xml.

See https://github.com/graalvm/native-build-tools/pull/146

v0.9.7

Compare Source

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:

<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

---

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.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.