[SPARK-53701] Use Java 25 toolchain while supporting Java 17+ #335
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dongjoon-hyun
force-pushed
the
SPARK-53701
branch
from
d88943b to
6f03aa7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
This PR aims to use Java 25 toolchain while supporting Java 17+.
Why are the changes needed?
After this PR, we can take advantage of Java 25 compiler improvements while supporting all Java 17+ versions via
options.release = 17.spark-kubernetes-operator/build.gradle
Line 59 in db7e640
Does this PR introduce any user-facing change?
Gradlewill automatically download and use it.Gradle WrapperdownloadsGradleitself, most of developers should get Java 25 without any issues.How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.