Require JDK 17 for building & update plugins and dependencies#2918
Merged
Conversation
The plugins and dependencies updated by this commit are related to the requirement of using JDK 17.
eamonnmcmanus
approved these changes
Oct 6, 2025
eamonnmcmanus
left a comment
Member
There was a problem hiding this comment.
Thanks! That's very helpful.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Require JDK 17 for building, and applies some of the version updates of #2914
Description
Applies the version updates of #2914 which require JDK 17 or newer. I have omitted the other version updates to keep this cleaner; they can be applies independently afterwards.
The CI build still runs on JDK 11 as well (but with a custom configuration) to ensure that Gson works on a version without Record classes properly as well.
Checklist
This is automatically checked by
mvn verify, but can also be checked on its own usingmvn spotless:check.Style violations can be fixed using
mvn spotless:apply; this can be done in a separate commit to verify that it did not cause undesired changes.null@since $next-version$(
$next-version$is a special placeholder which is automatically replaced during release)TestCase)mvn clean verify javadoc:jarpasses without errors