chore: use Java 17 for building pgjdbc, and use --release 8 to target Java 8, add tests with Java 21 and 22 #3026
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After this PR we will always use a recent JDK for building pgjdbc (e.g. a recent javac), and we will use toolchains to separate the build JDK from the test JDK.
For now, we will use Java 17 for building pgjdbc, and we could bump to Java 21 as Gradle 8.5 releases.
Fixes #3014
Workarounds applied
COPR_OWNER
is detected, then the default build JDK downgrades to 11. In the long term, we should update COPR configs to use Java 17JAVA_HOME_17_ARM64
intoJAVA_HOME_17_X86
to workaround Action fails at aarch64 machine since action.yml hardcodes X64 oracle-actions/setup-java#63Issues so far