I am not sure such feature is covered in the scope of sbt-native-packager, but it is highly helpful.
There is a feature request in other sbt plugin https://github.com/scalameta/sbt-native-image/issues/58, but it seems that the plugin is not so actively maintained.
Expected behaviour
sbt test runs tests with GraalVM native agent so metadata for native image build are collected automatically.
Actual behaviour
Such feature is not implemented.
Information
What sbt-native-packager are you using
1.10.0
What sbt version
1.9.9
What is your build system (e.g. Ubuntu, MacOS, Windows, Debian )
MacOs
What package are you building (e.g. docker, rpm, ...)
GraalVM native image
What version has your build tool (find out with e.g. rpm --version)
graalvm-22.3.1
What is your target system (e.g. Ubuntu 16.04, CentOS 7)
Background
Since 2019, GraalVM offers Java agent to collect native image configuration from running JVM app. GraalVM's official Gradle plugin offers support for the agent. It's user can collect configuration by
gradlew test metadataCopy
which dramatically help native image build workflow.I am not sure such feature is covered in the scope of sbt-native-packager, but it is highly helpful. There is a feature request in other sbt plugin https://github.com/scalameta/sbt-native-image/issues/58, but it seems that the plugin is not so actively maintained.
Expected behaviour
sbt test
runs tests with GraalVM native agent so metadata for native image build are collected automatically.Actual behaviour
Such feature is not implemented.
Information
rpm --version
)