[MASSEMBLY-567] Version wildcard in dependencySet include does not work

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2, 2.2.1
• Fix Version/s: 2.4
• Environment: Windows XP; maven 2.2.1, 3.0.3
• Assignee: Dennis Lundberg
• Reporter: Stephan Oudmaijer
• Created: 21/Jul/11 02:20
• Updated: 08/Apr/15 08:02
• Resolved: 27/Oct/12 14:22

Description

In our assembly descriptor we use a version wildcard for a dependencySet include, see the following snippet:

<dependencySet>
<outputDirectory>./configuration</outputDirectory>
<includes>
<include>com.xyz.admin:xyz-admin-tool-config:*:zip:config</include>
</includes>
<unpack>true</unpack>
</dependencySet>

This used to work in version 2.2-beta-5 but since 2.2 but also in 2.2.1 this does not work anymore. The version wildcard causes problems. According to the documentation:

Artifacts are matched by a set of identifier strings. In the following strings, type is 'jar' by default, and classifier is omitted if null.

groupId:artifactId:version:type:classifier ( artifact.getId() )

Any '*' character in an include/exclude pattern will result in the pattern being split, and the sub-patterns being matched within the three artifact identifiers mentioned above, using String.indexOf(..).

I suspect this is a bug? Or the behavior has changed, but this is not in-line with the documentation.

Issue Links

• is related to: MASSEMBLY-599 Mistake in javadoc for dependencySet/includes