You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @gfmedeiros,
This issue originates from svm.jar missing from the classpath during the plugin run.
You should be able to easily workaround that by setting JAVA_HOME=$GRAALVM_HOME.
As this is not that convenient, we actually added an explicit implementation dependency on svm.jar in this commit. That change will land in 0.9.14.
I'll close this issue, but feel free to comment if you have some other questions.
Fixed by #274
Hm that shouldn't happen...
I had a similar thing happen to me locally, and if I remember correctly it was an issue with SDKMAN installed JDKs being auto detected by Maven Toolchain support. Running mvn with -X might be useful for debugging this.
If you are able to build the latest version from master that would solve your problem, as we now pin both java executable and sdk dependency. We are still working on fixing our snapshot publishing CI task, so unfortunately there is no nice and quick way to check that out.
Describe the bug
The Maven plugin fails when when trying to build a native test binary. Building the actual binary works as expected.
To Reproduce
Use this reproducer.
Expected behavior
The test binary should be built successfully.
Logs
System Info (please complete the following information):
Linux Mint 20.3
22.1.0.0.r17-mandrel
17
native-gradle-plugin:0.9.13
The text was updated successfully, but these errors were encountered: