[native] Quarkus not able to parse GraalVM version in upcoming 21.1

Describe the bug

Quakus fails to parse the GraalVM version from native-image --version in upcoming GraalVM 21.1.

This is because in the upcoming GraalVM the version is:

GraalVM Version 21.0.0 (Java Version 11.0.10+8-jvmci-21.0-b06)

while in previous versions it used to be:

GraalVM 21.1.0 Java 11 CE (Java Version 11.0.11+5-jvmci-21.1-b02)

Note the removal of “Version” and the addition of “Java 11 CE”.

Expected behavior

Quarkus should be able to get the version without any warning or error.

Actual behavior

Quarkus prints:

[io.quarkus.deployment.pkg.steps.NativeImageBuildStep] Unable to get GraalVM version from the native-image binary.

To Reproduce

1. Grab GraalVM from https://github.com/graalvm/graalvm-ce-dev-builds/releases/tag/21.1.0-dev-20210330_0726
2. Build a Quarkus app or test with -Dnative and GRAALVM_HOME pointing to GraalVM 21.1.0-dev

[jerboaa]

why is it that native-image in mandrel can’t just do the same as graalvm native-image does and we adjust quarkus to attempt parse with both patterns?

I’m +1 to keeping with native-image --version logic.

We are looking to “align” with Graal VM for native-image --version via https://github.com/graalvm/mandrel/issues/230. but we cannot do it in full as a) Graal VM ships native image as native binary, Mandrel not (there is a risk shipping as native-image; rather than plain java app) b) Graal VM upstream would prefer not to call it Graal VM if it’s Mandrel (OpenJDK + native-image), not a native-image.

Either way, something needs to change. It’s just a matter of coming to an agreement how quarkus parses the native image version and what the expected inputs are going to be for Mandrel/Graal.

[jaikiran]

Graal releases have for a long time included a GRAALVM_HOME/release file which is a properties file and contains important and useful information like the Graal VM version, Java version and various other things. For example, the one I have in my 21.1.0-dev currently has this:

...

GRAALVM_VERSION="21.1.0-dev"
...
JAVA_VERSION="11.0.11"

So I think it’s time to start parsing this file instead of relying on the native-image --version output which is less reliable due to changes like these.