[MNG-4761] Plugin-level dependency scope causes some plugin classpaths to be incorrect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1, 3.0-beta-1, 3.0-beta-2
• Fix Version/s: 2.2.2, 3.0-beta-3
• Component/s: Artifacts and Repositories, Plugins and Lifecycle
• Flags: Patch
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 11/Aug/10 10:59
• Updated: 05/Apr/15 14:54
• Resolved: 11/Aug/10 14:54

Description

Plugin-level dependencies should use RUNTIME scope at all times. Using any other scope may alter the weighting given to the subgraph-choice algorithm used in transitive dependency resolution.

Plugin-level dependencies use compile scope by default. When transitive resolution takes place, compile scope takes precedence over runtime scope, causing the transitive dependency sub-graph of the plugin-level dependency to be activated over those of the plugin itself.

This happens even when the plugin's transitive dep is NEARER to the top level than the one brought in by that plugin-level dependency itself.

The result is that when a dep that's farther away is chosen over a nearer one, it can then be disabled by Maven choosing to disable its parent dep (the one that brought it in) in another part of the transitive resolution process.

This is a very subtle case where Maven is doing the wrong thing. The attached test case should make it clearer.

Issue Links

• is related to: MNG-4134 Conflict resolution with scope widening can cause transitive dependencies to be omitted
• relates to: MNG-4790 Dependency resolution issue with provided scope
• relates to: MNG-4800 Conflict resolution does not pick sub tree of nearest dependency if farther conflicting dependency has wider scope