[MNG-3408] Artifacts with the same pair groupId:artifactId but different type are not resolved independently

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.8
• Component/s: Dependencies
• Assignee: Benjamin Bentmann
• Reporter: Nicolas Malassigné
• Created: 18/Feb/08 11:00
• Updated: 09/Apr/10 12:16
• Resolved: 09/Apr/10 12:16

Description

This problem is preventing for instance parallel builds to run in a continuous server, without broken builds being falsely reported from time to time.

Ex:

• Project B is depending on artifacts from Project A.
• Builds for Project A and Project B are both triggered at the same time.
• The build of project A finishes earlier, so that Project A deploys its artifacts while Project B is still building (replacing the previous artifacts).

What can happen is that the build of Project B suddenly breaks, because it needs an artifact of Project A for which it already resolved the dependency, but yet of a different type. Maven is writing the local metadata file when resolving the pair groupId:artifactId of the first type, and is reading the same metadata file when resolving the same pair of the second type (which may come later in the build).

Actually I think that groupId:artifactId:type should be considered for the uniqueness of artifacts instead of groupId:artifactId, and this information be contained in the local metadata files.

Issue Links

• duplicates: MNG-4452 Metadata for snapshots should include classifier