maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-3426) regression : <dependency> in plugin configuration doesn't override plugin classpath
Date Sun, 02 Mar 2008 19:06:28 GMT

     [ http://jira.codehaus.org/browse/MNG-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

nicolas de loof updated MNG-3426:
---------------------------------

    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).

  was:
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.


> regression : <dependency> in plugin configuration doesn't override plugin classpath
> -----------------------------------------------------------------------------------
>
>                 Key: MNG-3426
>                 URL: http://jira.codehaus.org/browse/MNG-3426
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugin API
>    Affects Versions: 2.0.8
>            Reporter: nicolas de loof
>            Priority: Critical
>
> 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).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message