[MRELEASE-589] Resolved dependencies overwritten when multiple subprojects with SNAPSHOT dependencies are released

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.1
• Component/s: perform
• Flags: Patch
• Assignee: Brett Porter
• Reporter: Elliot Metsger
• Created: 13/Aug/10 06:47
• Updated: 05/Apr/15 14:54
• Resolved: 29/Sep/10 10:35

Description

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:

<project>
    ...
    <dependency>
      <groupId>external</groupId>
      <artifactId>artifactId</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
    ...
</project>

Given subproject two defines a snapshot on artifactId2:

<project>
    ...
    <dependency>
      <groupId>external</groupId>
      <artifactId>artifactId2</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
    ...
</project>

And you run

release:perform

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.

Issue Links

• is duplicated by: MRELEASE-303 Resolved SNAPSHOT versions are overwritten