Bump native-maven-plugin from 0.9.1 to 0.9.7

[dependabot]

Bumps native-maven-plugin from 0.9.1 to 0.9.7.

Release notes

Sourced from native-maven-plugin's releases.

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

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #117.