Update builder images to jdk-21

[zakkak]

• Update the GraalVM Community builder image to the tag jdk-21
• Update the Mandrel builder image to the tag jdk-21(Mandrel 23.1)
• Update GraalVM SDK version to 23.1 (yes, it does not follow the same version scheme)

Draft till the Mandrel images get pushed to quay.io.

[Sanne]

hi @zakkak, there are some conflicts

[gsmet]

@zakkak I rebased and added a few commits.

[gsmet]

FWIW, the VT thread CI is now failing in native as we use a builder that has apparently been dropped so we really need it now.

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Failing Jobs - Building a994576

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs
✖	JVM Tests - JDK 17 Windows	Build	⚠️ Check →	Logs	Raw logs
🚫	JVM Tests - JDK 20
✔️	Maven Tests - JDK 11
✖	Maven Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✖	Native Tests - Windows - RESTEasy Jackson	Setup GraalVM	⚠️ Check →	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/oidc-client-graphql/deployment 

📦 extensions/oidc-client-graphql/deployment

✖ io.quarkus.oidc.client.graphql.GraphQLClientUsingOidcClientTest.typesafeClientWithDefault - More details - Source on GitHub

io.quarkus.dev.appstate.ApplicationStartException: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.dev.appstate.ApplicationStateNotification.waitForApplicationStart(ApplicationStateNotification.java:58)
	at io.quarkus.runner.bootstrap.StartupActionImpl.runMainClass(StartupActionImpl.java:132)

---

⚙️ Maven Tests - JDK 11 Windows #

- Failing: integration-tests/maven 

📦 integration-tests/maven

✖ io.quarkus.maven.it.DevMojoIT.testExternalReloadableArtifacts line 1448 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.maven.it.DevMojoIT was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

✖ io.quarkus.maven.it.JarRunnerIT.testNonAsciiDir line 70 - More details - Source on GitHub

java.lang.AssertionError: 

Expecting actual:

✖ io.quarkus.maven.it.DevMojoIT.testExternalReloadableArtifacts line 1448 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.maven.it.DevMojoIT was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

✖ io.quarkus.maven.it.JarRunnerIT.testNonAsciiDir line 70 - More details - Source on GitHub

java.lang.AssertionError: 

Expecting actual:

[zakkak]

CI failures are irrelevant.

@gsmet I suggest we get this backported to 3.5.

Please note that the update to Mandrel 23.1 / GraalVM for JDK 21) results in warnings like the following:

Warning: The option '-H:IncludeResourceBundles=yasson-messages' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: The option '-H:ReflectionConfigurationFiles=reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: The option '-H:ReflectionConfigurationResources=META-INF/native-image/io.micrometer/micrometer-core/reflect-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: The option '-H:ReflectionConfigurationResources=META-INF/native-image/io.netty/netty-transport/reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: Please re-evaluate whether any experimental option is required, and either remove or unlock it. The build output lists all active experimental options, including where they come from and possible alternatives. If you think an experimental option should be considered as stable, please file an issue.

which should be fixed in the corresponding projects, e.g., as in netty/netty#13596 and micrometer-metrics/micrometer#4246

[zakkak]

Warning: The option '-H:ReflectionConfigurationFiles=reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.

The Warning: The option '-H:ReflectionConfigurationFiles=reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future. part is integration-tests/main specific and related to #36491

[gsmet]

Yeah I think it makes sense to backport it. The warnings are unfortunate though, thanks for creating PRs in the upstream projects.

[jerboaa]

Please note that the update to Mandrel 23.1 / GraalVM for JDK 21) results in warnings like the following:

Warning: The option '-H:IncludeResourceBundles=yasson-messages' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: The option '-H:ReflectionConfigurationFiles=reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: The option '-H:ReflectionConfigurationResources=META-INF/native-image/io.micrometer/micrometer-core/reflect-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: The option '-H:ReflectionConfigurationResources=META-INF/native-image/io.netty/netty-transport/reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: Please re-evaluate whether any experimental option is required, and either remove or unlock it. The build output lists all active experimental options, including where they come from and possible alternatives. If you think an experimental option should be considered as stable, please file an issue.

which should be fixed in the corresponding projects, e.g., as in netty/netty#13596 and micrometer-metrics/micrometer#4246

@zakkak Couldn't we work-around those warnings by using --exclude-config?

Non-standard options help:

    --exclude-config      exclude configuration for a comma-separated pair of classpath/modulepath
                          pattern and resource pattern. For example:
                          '--exclude-config foo.jar,META-INF\/native-image\/.*.properties'
                          ignores all .properties files in 'META-INF/native-image' in all
                          JARs named 'foo.jar'.

[zakkak]

For micrometer we could, but it won't work for all cases, e.g. for netty we also need to rename reflection-config.json to reflect-config.json, otherwise it won't be picked up by native-image.