[jira] Updated: (MNG-3890) Transitive dependencies override explicitly set scope.

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

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

Benjamin Bentmann updated MNG-3890:
-----------------------------------

    Affects Version/s: 3.0-alpha-1
                       2.1.0-M1

> Transitive dependencies override explicitly set scope.
> ------------------------------------------------------
>
>                 Key: MNG-3890
>                 URL: http://jira.codehaus.org/browse/MNG-3890
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
>            Reporter: Stephan Kleine
>            Priority: Critical
>         Attachments: testcase.tar.bz2
>
>
> Transitive dependencies override explicitly set scope.
> E.g. a project A depends on "Hibernate" with default scope and a project B depends on project A as well as on "Hibernate" for which it sets the scope explicitly to "provided". Further an EAR project C depends on project B (see the attached testcase).
> Now I would expect that C does not contain any jars for Hibernate and its dependencies since B explicitly set the scope to "provided". Sadly this is not the case and C contains all hibernate jars. The only way around this I have found is setting the scope to "provided" for Hibernate in A as well - which is just a crude hack that produces other issues.
> IMHO this is a bug because Maven should respect the overridden dependency scope since the current way forces me to set the scope to provided in A which is just wrong.
> Please try to get this fixed for 2.10 or 2.1 since it's a real pita atm.

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