[jira] Commented: (MNG-3196) Allow exclusion of a certain transitive dependency across all direct dependencies.

["Charles Canning (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154008#action_154008 ] 

Charles Canning commented on MNG-3196:
--------------------------------------

A way to probably attempt this without changing model in the pom would be to add an exclusion scope. So, something like

 <dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>3.8.1</version>
    <scope>exclusion</scope>
</dependency>

Not sure if this applies to the older bug or not.


> Allow exclusion of a certain transitive dependency across all direct dependencies.
> ----------------------------------------------------------------------------------
>
>                 Key: MNG-3196
>                 URL: http://jira.codehaus.org/browse/MNG-3196
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Dependencies
>    Affects Versions: 2.0.7
>            Reporter: Paul Gier
>             Fix For: 3.0
>
>
> I would like to be able to put exludes at the top level of dependencies so that it can easily be excluded from all transitive dependencies, instead of just excluding it from a single dependency at a time.  For example assume that project1 and project2 both have transitive dependencies on different versions of project-trans:
> <dependencies>
>   <exclusions>
>     <exclusion>
>       <groupId>com.stuff</groupId>
>       <artifactId>project-trans</artifactId>
>     </exclusion>
>   </exclusions>
>   <dependency>
>     <groupId>com.stuff</groupId>
>     <artifactId>project1</artifactId>
>     <version>1.0</version>
>   <dependency>
>   <dependency>
>     <groupId>com.stuff</groupId>
>     <artifactId>project2</artifactId>
>     <version>1.0</version>
>   <dependency>
> </dependencies>
> In this example, the "project-trans" dependency would be exluded from both project1 and project2.  It can be difficult to find all the locations of a transitively included dependency for a large project that has a large number of frequently changing dependencies.

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