Upgrade maven-compiler-plugin to 3.14.1 #6461
Open
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
Contributor
Author
|
ready for review |
Contributor
Author
|
ready for review @zoewangg |
sullis
changed the title
Contributor
Author
|
Ready for review. |
Member
|
Hi @sullis! Any motivation for the upgrade, besides being the latest version? For example, any particular bugfix you're hoping to get? |
debora-ito
added
the
no-api-surface-area-change
|
debora-ito
approved these changes
Jan 21, 2026
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation and Context
upgrade to latest maven-compiler-plugin: 3.14.1
https://github.com/apache/maven-compiler-plugin/releases
Modifications
pom.xml
Testing
CI build
Screenshots (if appropriate)
Types of changes
Checklist
mvn installsucceedsscripts/new-changescript and following the instructions. Commit the new file created by the script in.changes/next-releasewith your changes.License