You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/03/27 02:07:58 UTC
[jira] Commented: (MNG-3482) merging managed dependencies happens
before managed-dependency versions are interpolated
[ http://jira.codehaus.org/browse/MNG-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128817#action_128817 ]
John Casey commented on MNG-3482:
---------------------------------
fix is in place on both 2.0.x and trunk branches, but needs a unit test for completeness.
> merging managed dependencies happens before managed-dependency versions are interpolated
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3482
> URL: http://jira.codehaus.org/browse/MNG-3482
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.0.9, 2.1-alpha-1
> Reporter: John Casey
> Assignee: John Casey
>
> mergeManagedDependencies(..) happens ahead of processProjectLogic(..) inside the DefaultMavenProjectBuilder.buildInternal(..) method. This means that, if the current POM specifies an expression for one of the managed dependencies that have scope == import, the artifact resolver will fail to resolve the managed dependency with an uninterpolated version.
--
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