build: modernize all core lifecycle plugins for offline mirror compatibility#401
Merged
AnshulPatni merged 1 commit intoJul 10, 2026
Conversation
…ibility Change-Id: I6ebc691b30eb5572e2280178411bd9aed3d0d4cc
taeold
approved these changes
Jul 10, 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 building against Sonatype's
oss-parent:9, default lifecycle bindings execute legacy plugin versions from 2012–2014 (such asmaven-install-plugin:2.4andmaven-resources-plugin:2.6). These legacy plugins depend on deprecated transitive artifacts (plexus-components,spice-parent) that are unavailable in offline package mirrors.This PR defines modern, vetted versions for all 8 core lifecycle plugins (
enforcer,install,deploy,clean,resources,compiler,surefire, andjar) in rootpluginManagement. All specified versions and their parent POM chains have been audited to guarantee 100% compatibility with offline package mirrors during automated release builds.