maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5150) DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting the runtime classpath)
Date Tue, 04 Sep 2012 06:13:21 GMT

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

Anders Hammar updated MNG-5150:
-------------------------------

    Comment: was deleted

(was: I prematurely submitted this. Please do the following updates to the ticket:
Summary: DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting
the runtime classpath)
Description: See issue MJBOSSPACK-40 for details, especially Benjamin's clarifications on
difference between how Maven 2 and 3 behave. Test projects are available in that ticket.)
    
> DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting
the runtime classpath)
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-5150
>                 URL: https://jira.codehaus.org/browse/MNG-5150
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0, 3.0.1, 3.0.2, 3.0.3
>         Environment: any
>            Reporter: Anders Hammar
>
> See issue MJBOSSPACK-40 for details, especially Benjamin's clarifications on difference
between how Maven 2 and 3 behave. Test projects are available in that ticket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message