[ http://jira.codehaus.org/browse/MNG-1577?page=all ]
Ralph Goers updated MNG-1577:
-----------------------------
Attachment: mng1577c.patch
I've uploaded mng1557c.patch for maven-2.0.x. I updated the patch with these
changes:
1. The prior patch was creating a ManagedVersionMap several times for a
project. Now it just does it once.
2. If no dependencyManagement section is present then the parent
ManagedVersionMap is used instead of creating a clone.
3. If override is enabled then the scope in the dependencyManagement is not
used at all (only the version is used). If override is false then it continues
to override the scope for compatibility (although I can't imagine a case where
this would be desirable).
4. Dependencies in child dependencyManagement sections override their parents.
However, managed dependencies specified in the project will override transitive
dependencies even if they extend a pom containing the same managed dependency.
This is the desired behavior.
5. I tested building myfaces with an unmodifed maven, with override set to
false and with override set to true and didn't see any real difference in cpu.
The debug file is slightly larger due to a few extra debug log entries.
Please test this again and provide feedback.
> dependencyManagement does not work for transitive dependencies
> --------------------------------------------------------------
>
> Key: MNG-1577
> URL: http://jira.codehaus.org/browse/MNG-1577
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0
> Reporter: Joerg Schaible
> Fix For: 2.1
>
> Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch,
> mng1577c.patch, mng1577trunk.patch
>
>
> The dependencyManagement does not work for transient dependencies. The
> specified version is ignored.
> Use case:
> Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT
> and B-SNAPSHOT
> Project A is child of Main and depends directly on commons-beanutils (version
> inherited from Main)
> Project B is child of Main and depends directly on commons-digester (version
> inherited from Main)
> Project C is child of Main and depends directly on A & B (versions inherited
> from Main)
> A is compiled and tests are run using commons-beanutils-1.7.0
> B is compiled and tests are run using commons-digester-1.6 and
> commons-beanutils-1.6, since digester is dependend on this
> C is compiled and tests are run using commons-beanutils-1.7.0
> Integration tests of B did not verify, that B is behaving as expected in this
> scenario. B might fail with 1.7.0 and it is not even recognized.
> If I add beanutils also as direct dependency to B, it works fine, but then
> are transitive dependency useless. It should be possible to define at least
> in the dependencyManagement, that the versions of transient dependencies also
> defined in the dependencyManagement have priority.
> - Jörg
--
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
