[MNG-4056] Relax resolution of active project artifacts from the reactor with regard to artifact type

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.10, 2.1.0-M1
• Fix Version/s: 2.1.0, 3.0-alpha-3
• Component/s: Dependencies
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 27/Feb/09 05:52
• Updated: 10/Oct/11 10:11
• Resolved: 03/Mar/09 07:48

Description

Right now, active project artifacts from the reactor are resolved by their exact artifact id. The distinction between artifact type and classifier gives rise to confusion for users here. For instance, the test JAR attached by jar:test-jar has the id gid:aid:test-jar:version. Hence, resolution from the reactor cache works only if users specify the dependency on the test JAR with <type>test-jar</type>, omitting <type> and just giving <classifier>tests</classifier> will not resolve the dependendy from the reactor. However, the latter approach with the classifier works once the test JAR is installed to the local repo. EJB client JARs are another example of this issue.

Maybe we can extend the reactor resolution to do another id matching try which constructs the id of the active artifact by assuming type = artifactHandler.extension and classifier = artifactHandler.classifier before matching with the dependency id. This should more closely resemble artifact identity as visible in the repository, where we have no artifact type but only classifier and extension.

Issue Links

• is related to: MNG-2045 Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
• is related to: MNG-4248 CLONE -Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
• supercedes: MNG-4018 Maven doesn't resolve correct the dependency with classifier in the multi-part project.