search

graalvm / mandrel

Mandrel is a downstream distribution of the GraalVM community edition. Mandrel's main goal is to provide a native-image release specifically to support Quarkus.
Other
397 stars 15 forks source link

[CI] GraalVM CE build with --maven-deploy-local is broken #790

Closed jerboaa closed 2 months ago

jerboaa commented 2 months ago

Description

We build GraalVM CE with local maven deployment to verify the Quarkus build with it. This started to break since we derived the maven version from the maven-deploy.log which now has warnings. Thus the maven version gets incorrectly set to java.lang.System.

Excerpt from maven-deploy.log:

WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by org.fusesource.jansi.internal.JansiLoader in an unnamed module (file:/usr/share/apache-maven-3.8.8/lib/jansi-2.4.0.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by org.fusesource.jansi.internal.JansiLoader in an unnamed module (file:/usr/share/apache-maven-3.8.8/lib/jansi-2.4.0.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

Installing org.graalvm.sdk:collections...

Here is the Quarkus build which tries to use java.lang.System as the maven version of the GraalVM artefacts: https://github.com/graalvm/mandrel/actions/runs/10764397126/job/29847395901#step:10:19

jerboaa commented 2 months ago

In Mandrel Packaging we derive the maven version from mx graalvm-version instead of relying on the first line of the deploy log. That build doesn't have the issue. See: https://github.com/graalvm/mandrel/actions/runs/10764397126/job/29847289308#step:10:19