Skip to content

[4.0.x] Fix mvnup: use effective model to resolve properties from remote parents#12221

Closed
gnodet wants to merge 1 commit into
apache:maven-4.0.xfrom
gnodet:cherry-pick-12158-to-4.0.x
Closed

[4.0.x] Fix mvnup: use effective model to resolve properties from remote parents#12221
gnodet wants to merge 1 commit into
apache:maven-4.0.xfrom
gnodet:cherry-pick-12158-to-4.0.x

Conversation

@gnodet

@gnodet gnodet commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Cherry-pick of #12158

…mvnup (apache#12158)

The undefined property detection in CompatibilityFixStrategy only performed
static analysis of reactor POMs, missing properties inherited from remote
parent POMs. This caused valid dependencyManagement entries to be incorrectly
commented out, breaking child modules relying on them for version resolution.

Now uses buildEffectiveModel to collect properties from the full parent chain,
including remote parents resolved via relativePath or Maven repositories.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@gnodet gnodet closed this Jun 4, 2026
@gnodet gnodet deleted the cherry-pick-12158-to-4.0.x branch June 4, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant