[MNG-3426] regression : <dependency> in plugin configuration doesn't override plugin classpath

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.8
• Fix Version/s: 2.0.9
• Component/s: Plugin API
• Assignee: John Dennis Casey
• Reporter: nicolas de loof
• Created: 02/Mar/08 13:01
• Updated: 21/Mar/08 11:30
• Resolved: 21/Mar/08 11:05

Description

Many maven plugins are wrapper around other tools. The plugin is designed for a version of the tool, and in many case user will want to use a specific version without having to patch the plugin. The <dependency> element on plugin configuration is a common way to do this, by overriding the plugin POM dependency with another version.

<plugin>
<artifactId>castor-maven-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.codehaus.castor</groupId>
<artifactId>castor</artifactId>
<version>VERSION OF CASTOR I WANT TO USE FOR CODE GENERATION</version>
</dependency>
</dependencies>
</plugin>

This used to work with maven < 2.0.8

In maven 2.0.8, this doesn't work anymore as the <dependency> set in plugin configuration is added to plugin classpath, as a duplicate for the one declared by the plugin but LATER in the classpath (but I may be wrong on this analysis).

Issue Links

• is duplicated by: MNG-2972 Ignores version of plugin dependency specified in my pom
• relates to: MNG-3473 site generation with 2.0.9 and plugin:report (2.4 ONLY) is broken
• relates to: MNG-3119 Duplicate attached artifacts should not be allowed.

Sub-Tasks

• <dependency> in plugin configuration doesn't override maven-antrun-plugin classpath: Closed