Skip to content

Fix #12045: warn when effective model analysis fails for inherited plugins#12046

Merged
gnodet merged 3 commits into
masterfrom
ci-issue-12045
May 14, 2026
Merged

Fix #12045: warn when effective model analysis fails for inherited plugins#12046
gnodet merged 3 commits into
masterfrom
ci-issue-12045

Conversation

@gnodet
Copy link
Copy Markdown
Contributor

@gnodet gnodet commented May 13, 2026

Summary

  • Change log level from debug to warning when effective model analysis fails in PluginUpgradeStrategy, so users are informed when plugins inherited from remote parent POMs cannot be detected for upgrade
  • Fix standalone session transport configuration: register transporter factories via @Provides methods so they properly feed into the DI Map<String, TransporterFactory>. The previous approach of binding TransporterProvider directly was overridden by the @Provides method in RepositorySystemSupplier which received an empty factory map, leaving no HTTP transport available
  • Add test verifying the warning is emitted when effective model analysis fails for a POM with an unresolvable remote parent

Before

mvnup apply on accumulo-wikisearch silently reports "No plugin upgrades needed" for all 4 POMs, despite inheriting maven-enforcer-plugin:1.4.1 from org.apache:apache:23.

After

mvnup apply correctly detects and adds pluginManagement entries for 3 inherited plugins that need Maven 4 compatibility upgrades:

  • maven-enforcer-plugin3.0.0
  • maven-remote-resources-plugin3.0.0
  • maven-shade-plugin3.5.0

Closes #12045

Test plan

  • Existing PluginUpgradeStrategyTest tests pass (20 tests)
  • New test verifies warning is logged when effective model analysis fails for unresolvable parent
  • Manual test against accumulo-wikisearch confirms inherited plugins are now detected and upgraded

Claude Code on behalf of Guillaume Nodet

gnodet and others added 3 commits May 13, 2026 08:14
…ugins

Change the log level from debug to warning when effective model analysis
fails in PluginUpgradeStrategy, so users are aware when plugins inherited
from remote parent POMs cannot be detected for upgrade.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Register transporter factories via @provides methods so they properly
feed into the DI Map<String, TransporterFactory>, fixing the standalone
session's ability to resolve remote parent POMs from Maven Central.

The previous approach of binding TransporterProvider directly was
overridden by the @provides method in RepositorySystemSupplier which
received an empty factory map, leaving no HTTP transport available.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Verifies that the standalone session can resolve org.apache:apache:23
from Maven Central and detect maven-enforcer-plugin:1.4.1 in the
parent's pluginManagement as needing a Maven 4 compatibility upgrade.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gnodet gnodet added this to the 4.0.0-rc-6 milestone May 13, 2026
@gnodet gnodet merged commit 8c36c76 into master May 14, 2026
23 checks passed
@gnodet gnodet deleted the ci-issue-12045 branch May 14, 2026 19:05
@github-actions
Copy link
Copy Markdown

@gnodet Please assign appropriate label to PR according to the type of change.

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.

mvnup plugin upgrade strategy silently fails to detect inherited plugins from remote parent POMs

2 participants