[
http://jira.codehaus.org/browse/MASSEMBLY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101946
]
Walt Wang commented on MASSEMBLY-223:
-------------------------------------
The problem seems caused by maven-common-artifact-filters. It returns from a
loop to iterate on excludes. So only first exclude take effect.
MASSEMBLY-223.patch attached.
> 2-nd <exclude> element of <dependencySets>:<excludes> doesn't work
> ------------------------------------------------------------------
>
> Key: MASSEMBLY-223
> URL: http://jira.codehaus.org/browse/MASSEMBLY-223
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Eugene Voytitsky
>
> I suppose that order of dependencySets:excludes:exclude doesn't make sense.
> But it seems that the plugin has a bug -- 2-nd <exclude> element of
> <dependencySets>:<excludes> doesn't work at all!
> Having such a dependencySet
> <dependencySet>
> <unpack>false</unpack>
> <excludes>
> <exclude>org.eclipse.update.*</exclude>
> <exclude>org.eclipse.equinox.http.*</exclude>
> </excludes>
> </dependencySet>
> I receive warning about
> [WARNING] The following patterns were never triggered in this artifact
> exclusion filter:
> o 'org.eclipse.equinox.http.*'
> When I change the order of exclude elements
> <dependencySet>
> <unpack>false</unpack>
> <excludes>
> <exclude>org.eclipse.equinox.http.*</exclude>
> <exclude>org.eclipse.update.*</exclude>
> </excludes>
> </dependencySet>
> I receive warning about
> [WARNING] The following patterns were never triggered in this artifact
> exclusion filter:
> o 'org.eclipse.update.*'
> So, as you can see the both exclude patterns are workable, but 2-nd one
> doesn't work independently of the element order.
--
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
