Armin Bauer created MVERSIONS-179:
-------------------------------------
Summary: Versions in dependencyManagement not updated
Key: MVERSIONS-179
URL: https://jira.codehaus.org/browse/MVERSIONS-179
Project: Maven 2.x Versions Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Armin Bauer
Attachments: resolveranges.patch
For a pom which just uses the dependencyManagement, the version ranges are not
updated using versions:resolve-ranges (in a parent pom for example). The
version are only resolved if the dependency is also included in the normale
dependencies sections outside of the dependencyManagement.
The following dependency for example would not be resolved:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.rabbitmq</groupId>
<artifactId>amqp-client</artifactId>
<version>(,4.0.0)</version>
</dependency>
</dependencies>
</dependencyManagement>
The background:
The resolveRanges function in the ResolveRangesMojo class uses the
findArtificats function to locate the artificate to resolve the version range.
The findArtifacts function iterates over the artificates listed in the
dependecies section of the pom and ignores all artifacts listed in the
dependencyManagement section. Therefore the artifact can only be resolved if it
is listed in both sections
The fix:
Use the toArtificate function instead which also works correctly for
dependencyManagement (see attached patch against 1.3.1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
