[MNG-4276] Plugins with indirect dependency on plexus-utils are stuck with plexus-utils:1.1

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.6
• Fix Version/s: 3.0-alpha-3
• Component/s: Class Loading, Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 02/Aug/09 05:20
• Updated: 02/Aug/09 08:09
• Resolved: 02/Aug/09 06:01

Description

To compensate the effect that MNG-2892 would have on bad plugins, a hack was put into the core that automagically injects plexus-utils:1.1 as a direct plugin dependency if the plugin does not already declare a direct dependency on plexus-utils:1.1+. However, only checking the plugin's direct dependencies for plexus-utils ignores any version of plexus-utils that is used by a transitive dependency. This corrupts the runtime class path of the plugin and can result in linkage errors like reported in AW: NPE with maven-changelog-plugin and git.

Issue Links

• is related to: MNG-2892 Use shade to hide the use of plexus-utils internally so that plugins can use their own version
• relates to: MNG-4274 Plugins with an undeclared but transitive dependency on plexus-utils via a core artifact get wrong version of p-u