build: switch to Java 17 for all modules #388
Open
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.
BREAKING CHANGE: this might break consumers running older Java versions
We've been seeing occasional compilation errors where the Gradle toolchain JDK auto detection picked up a Java 11 JDK which does not work with some of the newer syntax being used especially in unit tests.
The behavior was a bit random, sometimes it picked up Java 17 and the build went through, other times it picked up Java 11 and failed to compile.
I would propose to switch all modules to Java 17. This made the compilation more reliable for me locally.
I had to configure one JVM arg for the Spark tests to run successfully since something in those tests tries to access a protected module.