[MNG-3819] [regression] Plugins that don't declare dependency on plexus-utils no longer get plexus-utils:1.1

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-1
• Fix Version/s: 3.0-alpha-3
• Component/s: Class Loading, Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 07/Nov/08 05:54
• Updated: 20/Jun/22 05:58
• Resolved: 21/Oct/09 16:25

Description

To compensate for MNG-2892, Maven 2.0.6+ automatically injects plexus-utils:1.1 into the plugin class realm if the plugin POM does not declare a (direct) dependency on plexus-utils:1.1+. This backward-compat mode is currently not existent in Maven 3.x.

Even if this break is intentional for 3.x, this issue allows to track it.

Issue Links

• is related to: MNG-6825 Cleaning Up dependencies plexus-utils/maven-shared-utils/commons-lang3/commons-io
• is related to: MCHANGELOG-89 Dependency Conflict plexus-utils
• is related to: MNG-2892 Use shade to hide the use of plexus-utils internally so that plugins can use their own version
• is superceded by: MNG-6965 Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath