You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/12/18 23:00:55 UTC

[jira] Closed: (MNG-4501) Support global dependency excludes

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

Benjamin Bentmann closed MNG-4501.
----------------------------------

    Resolution: Duplicate
      Assignee: Benjamin Bentmann

> Support global dependency excludes
> ----------------------------------
>
>                 Key: MNG-4501
>                 URL: http://jira.codehaus.org/browse/MNG-4501
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>          Components: Dependencies
>            Reporter: Simon Brandhof
>            Assignee: Benjamin Bentmann
>
> The example that everybody understands : how to exclude commons-logging from dependencies ?  
> * explicitly exclude it from all transitive dependencies :
> {code}
> <dependency>
>   <groupId>commons-configuration</groupId>
>   <artifactId>commons-configuration</artifactId>
>   <exclusions>
>      <exclusion>
>         <groupId>commons-logging</groupId>
>         <artifactId>commons-logging</artifactId>
>       </exclusion>
>     </exclusions>
> </dependency>
> {code}
> * use the [Version 99 Does Not Exist|http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html] workaround.
> The best solution would be to add a section to the pom, for example :
> {code}
> <dependencies>
>   <exclusions>
>      <exclusion>
>         <groupId>commons-logging</groupId>
>         <artifactId>commons-logging</artifactId>
>       </exclusion>
>     </exclusions>
> </dependencies>
> {code}    

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