maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MASSEMBLY-141) Should be able to specify all dependency qualifiers, including "classifier"
Date Fri, 27 Oct 2006 19:23:03 GMT
     [ http://jira.codehaus.org/browse/MASSEMBLY-141?page=all ]

John Casey closed MASSEMBLY-141.
--------------------------------

         Assignee: John Casey
       Resolution: Fixed
    Fix Version/s: 2.2

You can now use wildcard matches on any part of Artifact.getId(). So, to isolate all where
type == 'war', you might use:

<includes>
  <include>*:war:*</include>
</includes>

> Should be able to specify all dependency qualifiers, including "classifier"
> ---------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-141
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-141
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1
>            Reporter: Simon Gunzenreiner
>         Assigned To: John Casey
>             Fix For: 2.2
>
>
> The AssemblyIncludesArtifactFilter class currently only uses groupId and classId to filter
dependencies, but it would be very useful to be able to filter on other dependency qualifiers
as well - in particular the "classifier".
> I would like to be able to filter jar files with the "sources" classifier (I assume this
is a classifier) when creating an assembly, to put those source archive files in a different
directory.

-- 
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

        

Mime
View raw message