Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0.8
-
Fix Version/s: 2.0.9
-
Component/s: Plugin API
-
Labels:None
-
Number of attachments :
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
1. |
<dependency> in plugin configuration doesn't override maven-antrun-plugin classpath | |
|
Unassigned |
Activity
| Field | Original Value | New Value |
|---|---|---|
| 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. This used to work with maven < 2.0.8 In maven 2.0.8, this doesn't work anomire as the <dependency> set in plugin configuration is added to classpath, as a duplicate for the on declared by the plugin but LATER in the classpath. |
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). |
| Fix Version/s | 2.0.9 [ 13801 ] | |
| Assignee | nicolas de loof [ ndeloof ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Assignee | nicolas de loof [ ndeloof ] | John Casey [ jdcasey ] |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |