Resolved dependencies overwritten when multiple subprojects with SNAPSHOT
dependencies are released
---------------------------------------------------------------------------------------------------
Key: MRELEASE-589
URL: http://jira.codehaus.org/browse/MRELEASE-589
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: perform
Affects Versions: 2.0
Reporter: Elliot Metsger
Attachments: Fix.patch, Testcase.patch
The CheckDependencySnapshotsPhase does not properly maintain the Set of
resolvedDependencies when there are multiple sub projects that have SNAPSHOT
deps.
Given subproject one defines a snapshot on _artifactId_:
{code}
<project>
...
<dependency>
<groupId>external</groupId>
<artifactId>artifactId</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
...
</project>
{code}
Given subproject two defines a snapshot on _artifactId2_:
{code}
<project>
...
<dependency>
<groupId>external</groupId>
<artifactId>artifactId2</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
...
</project>
{code}
And you run {code}release:perform{code} on the parent project and resolve the
snaps, I think you should expect the
{{ReleaseDescriptor.getResolvedSnapshotDependencies()}} to contain two entries:
* {{groupId:artifactId}}
* {{groupId:artifactId2}}
But instead it only contains the most recently resolved dependency.
--
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
