Relax resolution of active project artifacts from the reactor with regard to
artifact type
------------------------------------------------------------------------------------------
Key: MNG-4056
URL: http://jira.codehaus.org/browse/MNG-4056
Project: Maven 2
Issue Type: Wish
Components: Dependencies
Affects Versions: 2.1.0-M1, 2.0.10
Reporter: Benjamin Bentmann
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.
--
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
