maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Allen (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-1977) Global dependency exclusions
Date Tue, 30 Oct 2007 19:38:06 GMT

    [ http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112122
] 

Dan Allen commented on MNG-1977:
--------------------------------

I don't know, I will miss all of the late nights and long weekends I spend analyzing the dependency
tree trying to get rid of one stupid JAR file that causes the application not to run properly.
What will I do with all my extra time? Wow, maybe I can actually DEVELOP something.

> Global dependency exclusions
> ----------------------------
>
>                 Key: MNG-1977
>                 URL: http://jira.codehaus.org/browse/MNG-1977
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: POM
>            Reporter: Kees de Kooter
>             Fix For: 2.1
>
>
> I depend on some libraries, which in turn depend on something
> (which in turn depend on something) that I don't want, because I declare
> some other artifact in my pom.xml.
> A concrete example: I don't want that the artifact "xerces" is imported in
> my project because I declare to depend on  "xercesImpl" which ships newer
> libraries but with the same namespaces.
> I guess I would need an "exclude transitive dependency at all", either
> globally or from this and that artifact. I saw the <exclusions> tag, but it
> forces me to be very verbose and have exact control on what is required by a
> dependency.

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