You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2008/07/04 04:22:33 UTC
[jira] Updated: (MNG-3483) merging managed dependencies should ONLY
work when scope == import explicitly
[ http://jira.codehaus.org/browse/MNG-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-3483:
-------------------------------
Fix Version/s: (was: 2.1-alpha-1)
2.1-alpha-2
> merging managed dependencies should ONLY work when scope == import explicitly
> -----------------------------------------------------------------------------
>
> Key: MNG-3483
> URL: http://jira.codehaus.org/browse/MNG-3483
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.1-alpha-1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1-alpha-2
>
>
> dependencies of type == pom are useful for standardizing a set of dependencies for use in multiple projects that don't share a dependencyManagement section or a common parent POM. Limiting their use to import operations will severely curtail this option, and can cause a lot of problems with existing builds where modules have a type == pom, and are listed in dependencyManagement so they can be referenced elsewhere.
> This is related to MNG-3391, so I'll also link them.
--
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