[
https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312464#comment-312464
]
Dennis Lundberg commented on MASSEMBLY-567:
-------------------------------------------
Benson,
In short - the docs were a mess. There were at least 3 different specs. Look at
the issues that was resolved as part of the commit and follow the links in
those issues to see the different specs in the current docs. What I did was
align them so that they all tell the same story - the correct story.
> Version wildcard in dependencySet include does not work
> -------------------------------------------------------
>
> Key: MASSEMBLY-567
> URL: https://jira.codehaus.org/browse/MASSEMBLY-567
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2, 2.2.1
> Environment: Windows XP
> maven 2.2.1, 3.0.3
> Reporter: Stephan Oudmaijer
> Assignee: Dennis Lundberg
> Priority: Critical
> Fix For: 2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
