[MASSEMBLY-223] 2-nd <exclude> element of <dependencySets>:<excludes> doesn't work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2-beta-1
• Fix Version/s: 2.2-beta-2
• Flags: Patch
• Assignee: John Dennis Casey
• Reporter: Eugene Voytitsky
• Created: 25/Jun/07 12:42
• Updated: 05/Apr/15 14:44
• Resolved: 15/Aug/07 18:27

Description

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.