[24.1] Backport JDK 23+26 upgrade changes to 24.1 release tree

[jerboaa]

Backport oracle#9078

[jerboaa]

CI run with this: https://github.com/graalvm/mandrel/actions/runs/9660331969

[jerboaa]

CI run with this: https://github.com/graalvm/mandrel/actions/runs/9660331969

Summary of test failures is as follows (some of them we saw during nightly CI testing of graal/master when JDK 23 was the latest JDK release):

• Q IT Messaging1: quarkus-integration-test-kafka-oauth-keycloak native integration failure due to: [JDK 23+15] org.apache.kafka.common.security.oauthbearer.internals.OAuthBearerSaslClientCallbackHandler.handleCallback fails with UnsupportedOperationException quarkusio/quarkus#39634. Known issue.
• Q IT Data6: quarkus-integration-test-hibernate-search-orm-elasticsearch-outbox-polling fails due to a version parsing issue of 23-beta as reported in [JDK 23/22 EA] quarkus-integration-test-hibernate-search-orm-elasticsearch-outbox-polling native integration test fails due to NumberFormatException quarkusio/quarkus#39664 (caused by this upstream awaitability issue: JavaVersionDetector class fails with NumberFormatException on Temurin JDK 23 EA builds awaitility/awaitility#277). Known issue.
• Mandrel IT test failures are:
  • DynamicProxyConfigurationResources related warnings. Tracked in Allow list DynamicProxyConfigurationResources related warning so as to reduce test noise Karm/mandrel-integration-tests#261
  • AWT imageio test fails to generate images. Tracked in [24.1] imageio AWT tests fail with JDK 23 ea Karm/mandrel-integration-tests#262

[jerboaa]

@zakkak Could you please take a look? This would unbreak the JDK 23-based builds from the release branch.

[zakkak]

Thank you @jerboaa!

In general I am in favor of cherry picking the commits with the -x flag to make it easier to track backports back to the original commits but in this case the original PR consists of 44 commits...

So I am thinking that in this case maybe we could amend the commit message to include the commit messages and hashes of the backported commits and rebase? (skipping the empty automated ones)

Please let me know if you would like me to take this over.

[zakkak]

Futhermore, oracle#9078 is most probably going to be backported upstream as well so this is just an "early backport" for us to get testing working again, right?

[jerboaa]

Futhermore, oracle#9078 is most probably going to be backported upstream as well so this is just an "early backport" for us to get testing working again, right?

Yes, it'll be an early backport.

In general I am in favor of cherry picking the commits with the -x flag to make it easier to track backports back to the original commits but in this case the original PR consists of 44 commits...

So I am thinking that in this case maybe we could amend the commit message to include the commit messages and >hashes of the backported commits and rebase? (skipping the empty automated ones)

Wow, that seems like a bit of a waste of time in this case. I'm thinking of pushing this, then do git revert <sha> and merge the upstream changes once available.

Please let me know if you would like me to take this over.

If you feel like it's worth going this route of cherry-picking 44 commits then yes, please, take it over.

[zakkak]

Closing in favor of #757