Support Java 17

[maxandersen]

Description

Java 17 is out and Quarkus JVM works with Java 17 but native image needs updating and devtools/code quarkus not fully covered.

Using this epic to track status

Analysis

(links to analysis docs containing architecture design work, requirements gathering, etc)

• Support for java 17 in generated projects - Codestarts  #20849
• Java 17 records don't work in native image with GraalVM 21.3.0 JDK 17 #20891
• Integration tests using postgresql fail to compile natively with Java 17 #21359
• Integration tests using avro fail to compile natively with GraalVM CE 21.3 Java 17 #21370
• [GraalVM 21.3.0.r17] Optaplanner Native Build Failure #992 quarkus-quickstarts#993
• [GraalVM 21.3.0.r17] Kogito quickstarts build failure with Java 17 quarkus-quickstarts#991
• [GraalVM 21.3.0.r17] Class initialization of sun.lwawt.macosx.CInputMethod failed quarkus-quickstarts#989
• [GraalVM 21.3.0.r17] PostGres Native Issue quarkus-quickstarts#988
• Integration test bouncycastle-fips fails to compile natively with GraalVM CE 21.3 Java 17 #21374
• Integration test jgit fails to compile natively with GraalVM CE 21.3 Java 17 #21372
• runjava.sh in docker images not consistent between java 11 and java 17 #23045 run-java.sh

[famod]

One question here would be about CI (or nightly jobs). Do we need more Java 17 coverage? It seems so.

[maxandersen]

good question @famod - what java 17 coverage do we actually have enabled in CI now ?

[famod]

The following modules are not executed with Java 17:

• integration-tests/devtools changed in Run devtools ITs also with Java 17 #21903
• integration-tests/gradle
• integration-tests/maven
• tcks

Plus: No native tests, AFAICS, but I'm not really up to date with which GraalVM version we are running currently.

Ironically, the nightly EA job (using 18-ea currently) is covering all those (except native).
PS: Seems I forgot to create a houskeeping issue after #20340.

[zakkak]

@famod regarding native-image testing I am planning to create pipelines for testing Quarkus (running its integration tests) with Mandrel on Java 17. This would give us some info, but it would of course not ensure that no breaking changes make it to Quarkus moving forward.

Plus: No native tests, AFAICS, but I'm not really up to date with which GraalVM version we are running currently.

We are currently running with 21.3-java11

[zakkak]

FYI all native integration tests are now green with GraalVM CE 21.3-java17.

Note, the --add-exports added to resolve the issues in native mode:

• Export module sun.security.action for DB2 jdbc driver #21886
• Export sun.security.internal.spec module for bouncycastle in Java 17 #21785
• Temporary fix for failure to resolve 'sun.management.Util' when using GraalVM CE 21.3.0 Java 17  #21408
• Fix Kerberos module use in Java 17 #21550

will probably be needed in JVM-mode as well to avoid unpleasant surprises once the APIs in those modules get accessed at runtime.

[famod]

Devtools ITs are now also running with Java 17 in CI.

[zakkak]

@maxandersen You might want to include oracle/graal#4006 as well

[michael-simons]

Records do fail also with Qute. No warnings / errors on build time, but on runtime

Caused by: io.quarkus.qute.TemplateException: Property "value" not found on the base object "de.jcvogt.girlswhoviking.Quiz$Answer" in expression {foo.value} in template index.qute.html on line 24

when applying @RegisterForReflection, same error as in #20891

[vukzeka]

I agree with @zakkak this list should include oracle/graal#4006

[maxandersen]

All issues here are resolved and closed. We support Java 17 for a while now - anything else found is considered a bug.