-
Notifications
You must be signed in to change notification settings - Fork 505
Bump the min Gradle and Java requirements to 7.3 and 17 #2540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
Will finish this later. |
cfe3e40 to
7def050
Compare
d94d9c2 to
70d0787
Compare
|
This is a significant change; the next Gradle plugin release should be 7.1 or another minor version. |
|
Amazing! Bumping to Gradle Whatever path we choose, this PR is a great starting point. But my first instinct is that we should keep our current compat (Java 11 and Gradle 6.1.1) and then go straight to Java 17 and Gradle 7.3. Does that make sense, or is there a reason to retain support for Gradle 7.1 that I am missing? |
254896e to
3b66bf0
Compare
|
I'm fine with dropping Java 11 support. |
d3e013e to
62973f7
Compare
| @Test | ||
| @EnabledForJreRange(max = JAVA_15) // google-java-format requires JRE 11+ | ||
| void behavior18() throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
com.diffplug.spotless.Lint$ShortcutException: You are running Spotless on JVM 23. This requires google-java-format of at least 1.17.0 (you are using 1.8).
This is strange.
a410746 to
4af88e5
Compare
4af88e5 to
4c80f8e
Compare
|
Published in |
### What changes were proposed in this pull request? This PR aims to upgrade `Spotless` to 8.0.0 and remove `google-java-format` setting because it's equal to the default now. ### Why are the changes needed? To bring the latest improvements and bug fixes: - https://github.com/diffplug/spotless/releases/tag/gradle%2F8.0.0 - diffplug/spotless#2540 - diffplug/spotless#2345 - diffplug/spotless#2404 ### Does this PR introduce _any_ user-facing change? No. This is a test change. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #399 from dongjoon-hyun/SPARK-53988. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
No description provided.