Skip to content

Fix mvnup version normalization and artifact ID for plugin upgrades#12176

Closed
gnodet wants to merge 1 commit into
masterfrom
fix/mvnup-version-normalization
Closed

Fix mvnup version normalization and artifact ID for plugin upgrades#12176
gnodet wants to merge 1 commit into
masterfrom
fix/mvnup-version-normalization

Conversation

@gnodet
Copy link
Copy Markdown
Contributor

@gnodet gnodet commented May 28, 2026

Summary

  • Fix maven-compiler-plugin minimum version from 3.2.0 to 3.2 — version 3.2.0 does not exist on Maven Central, causing resolution failures (e.g. servicemix4-bundles, synapse)
  • Fix exec-maven-plugin entry in PLUGIN_UPGRADES to use the correct groupId (org.codehaus.mojo) and artifactId (exec-maven-plugin) — was incorrectly listed as org.apache.maven.plugins:maven-exec-plugin, inconsistent with getPluginUpgradesMap()

Test plan

  • PluginUpgradeStrategyTest — all 27 tests pass

🤖 Generated with Claude Code

maven-compiler-plugin was listed as 3.2.0 but that version does not
exist on Maven Central (only 3.2 exists), causing resolution failures.

exec-maven-plugin was listed with wrong groupId (org.apache.maven.plugins)
and artifactId (maven-exec-plugin), inconsistent with getPluginUpgradesMap().

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gnodet
Copy link
Copy Markdown
Contributor Author

gnodet commented Jun 1, 2026

Closing as duplicate of #12172 which fixes the same compiler 3.2.0→3.2 and exec-maven-plugin groupId/artifactId issues.

Claude Code on behalf of Guillaume Nodet

@gnodet gnodet closed this Jun 1, 2026
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