Repository navigation
fix(java): declare maven-install-plugin once in the java module - #985
Merged
SemyonSinchenko merged 1 commit intoOct 10, 2026
Merged
Conversation
The java module's pluginManagement declared maven-install-plugin twice, 2.5.1 without a groupId and 2.5.2 with it, both resolving to the same plugin. Maven already used 2.5.2 and only warned, but the CI runner now rejects the duplicate while reading the reactor, so the Java SDK format check fails before building. Dropping the shadowed 2.5.1 entry keeps the effective model unchanged.
SemyonSinchenko
approved these changes
Oct 10, 2026
3 of 4 tasks
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.
Reason for this PR
Closes #984.
maven-projects/java/pom.xmldeclaresmaven-install-plugintwice inpluginManagement; the CI runner now rejects that while loading the reactor, so the Java SDK format check fails before any module builds.What changes are included in this PR?
Removes the shadowed
maven-install-plugin2.5.1 declaration. The effective model is unchanged:help:effective-pomalready resolved 2.5.2.Are these changes tested?
mvn -f maven-projects/pom.xml -pl java validatesucceeds and themust be uniquewarning is gone. CI exercises the full reactor.Are there any user-facing changes?
No.
Checklist
make cpplintbefore submitting when changed files are in thecppdirectory.pre-commit runbefore commit the changed files.