You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2011/08/07 14:51:54 UTC

[jira] Commented: (MNG-5150) DepMgmt does incorrect scope updates of child deps of a profivedaffecting the runtime classpath

    [ https://jira.codehaus.org/browse/MNG-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275196#comment-275196 ] 

Anders Hammar commented on MNG-5150:
------------------------------------

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 does incorrect scope updates of child deps of a profivedaffecting 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
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira