[ http://jira.codehaus.org/browse/MNG-717?page=all ]
John Casey updated MNG-717:
---------------------------
Remaining Estimate: 3 hours
Original Estimate: 10800
> dependency doesn't allow dependencyManagement to provide scope
> --------------------------------------------------------------
>
> Key: MNG-717
> URL: http://jira.codehaus.org/browse/MNG-717
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> By design, DependencyManagement values are only used if the local POM doesn't
> provide values. In this way, if DependencyManagement provides a scope ==
> 'test' for junit, and the local POM doesn't specify a scope for junit, junit
> should have the scope 'test' assigned to it when the depMgmt is injected.
> HOWEVER, since the default value for Dependency.scope appears to be 'compile'
> it always has a value, and the DependencyManagement value can never take
> effect.
> The solution is to allow a null scope in the Dependency, and apply the
> default scope value later, either in the Artifact creation process, or during
> transitive resolution.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
