build: modernize utility Maven plugins for offline mirror compatibility#403
Merged
AnshulPatni merged 1 commit intoJul 11, 2026
Merged
Conversation
Change-Id: I334041630dff058d6460e5399f654867edb85599
taeold
approved these changes
Jul 11, 2026
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
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.
When packaging test dependencies during build validation (e.g.,
invoker/testfunction), Maven executedmaven-dependency-plugin:2.8(from 2013). This legacy version relies on deprecated transitive artifacts (commons-cli:1.0from 2002) that are unavailable in offline package mirrors.While our previous modernization covered all 8 core lifecycle plugins, this PR extends root
pluginManagementto define modern, vetted versions for all remaining utility and specialized plugins (dependency:3.6.1,shade:3.5.3,plugin:3.10.2, andrelease:3.0.1). All specified versions and their parent POM trees have been audited to guarantee 100% compatibility with offline package mirrors during automated release builds.