Skip to content

Filter project repos with uninterpolated property expressions#12204

Open
gnodet wants to merge 2 commits into
apache:masterfrom
gnodet:fix/filter-unresolvable-project-repos
Open

Filter project repos with uninterpolated property expressions#12204
gnodet wants to merge 2 commits into
apache:masterfrom
gnodet:fix/filter-unresolvable-project-repos

Conversation

@gnodet
Copy link
Copy Markdown
Contributor

@gnodet gnodet commented Jun 1, 2026

Summary

  • mvnup fix: Comment out repositories with undefined property expressions during mvnup apply (commit 1)
  • Runtime fix: Downgrade model validation for uninterpolated ${...} expressions in repository IDs/URLs from ERROR to WARNING, and filter such repositories in DefaultProjectBuildingHelper.createArtifactRepositories() before they reach the resolver (commit 2)
  • Analogous to the existing filtering in DefaultArtifactDescriptorReader.filterUninterpolated() for transitive dependency repos (PR Transitive dependency POMs with uninterpolated repository IDs cause build failures #12086), but for project-defined repositories

Fixes runtime failures like InternalErrorException: Not fully interpolated remote repository ${eclipseP2RepoId} seen in projects such as uima-uimaj, opennlp-sandbox, and seatunnel-shade whose POMs define repositories with property expressions that are never defined.

Test plan

  • Updated DefaultModelValidatorTest — uninterpolated expression checks now expect warnings instead of errors
  • Updated integration tests MavenITgh11140RepoInterpolationTest and MavenITgh11140RepoDmUnresolvedTest — builds succeed with warnings instead of failing
  • Verified with uima-uimaj: after mvnup apply, mvn validate succeeds with warning Skipping repository '${eclipseP2RepoId}' ... instead of the previous fatal error
  • All unit tests pass (impl/maven-impl, impl/maven-core, compat/maven-model-builder)
  • mvnup compatibility fix strategy tests pass

🤖 Generated with Claude Code

Projects like uima-uimaj, opennlp-sandbox, and seatunnel-shade define
repositories with ${eclipseP2RepoId} in the repo ID. This property is
never defined — it was used as a literal string in Maven 3. Maven 4
rejects it with IllegalArgumentException at runtime.

Extend the mvnup compatibility fix strategy to detect and comment out
repositories and plugin repositories whose id or url contain undefined
property expressions, following the same pattern used for dependencies
(apache#12080). Handles both root-level and profile-level repositories.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gnodet gnodet added this to the 4.0.0-rc-6 milestone Jun 1, 2026
gnodet added a commit that referenced this pull request Jun 1, 2026
#12204)

Cherry-pick from fix/filter-unresolvable-project-repos branch.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
gnodet added a commit that referenced this pull request Jun 1, 2026
#12204)

Cherry-pick from fix/filter-unresolvable-project-repos branch.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When a project POM defines repositories with ${...} expressions that
cannot be resolved (e.g. ${eclipseP2RepoId}), Maven 4 previously
failed with InternalErrorException. This change downgrades the model
validation from ERROR to WARNING and filters such repositories before
they reach the resolver, logging a warning instead of failing the build.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gnodet gnodet changed the title mvnup: comment out repositories with undefined property expressions Filter project repos with uninterpolated property expressions Jun 2, 2026
gnodet added a commit that referenced this pull request Jun 2, 2026
…(PR #12204)

Cherry-pick from fix/filter-unresolvable-project-repos branch.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

2 participants