[ 
https://jira.codehaus.org/browse/MNG-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277029#comment-277029
 ] 

Jesse Glick commented on MNG-4056:
----------------------------------

The fix of this bug looks like it obsoletes the caveat given at the end of 
http://maven.apache.org/guides/mini/guide-attached-tests.html. If that is 
right, perhaps the guide should go back to recommending 
{{<classifier>tests</classifier>}}, or explain that either style will work 
equally well.

> Relax resolution of active project artifacts from the reactor with regard to 
> artifact type
> ------------------------------------------------------------------------------------------
>
>                 Key: MNG-4056
>                 URL: https://jira.codehaus.org/browse/MNG-4056
>             Project: Maven 2 & 3
>          Issue Type: Wish
>          Components: Dependencies
>    Affects Versions: 2.0.10, 2.1.0-M1
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 2.1.0, 3.0-alpha-3
>
>         Attachments: MNG-4056.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to