maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-3775) Problem in dependency resolution with exclusion, pom parent
Date Tue, 30 Sep 2008 10:34:45 GMT

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

Joerg Schaible commented on MNG-3775:
-------------------------------------

This works as designed. The dependencyManagement section of a parent POM will always overwrite
any transient dependency (version, scope and exclusions). That's what it is used for.

> Problem in dependency resolution with exclusion, pom parent
> -----------------------------------------------------------
>
>                 Key: MNG-3775
>                 URL: http://jira.codehaus.org/browse/MNG-3775
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.9
>            Reporter: Bertrand Paquet
>         Attachments: bug_maven.zip
>
>
> See projects in attachement.
> Parent projet uses SEAM pom parent, and declares jboss-seam as dependency, excluding
javax.el
> First project uses parent project, and declares javax.el as dependency
> mvn dependency:list on first, you can see javax.el
> Second project uses parent project, and declares first project as dependency. It should
have javax.el on classpath (because of first project), but it doesn't.
> mvn dependency:list on second, javax.el disappears !

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