maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Oudmaijer (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MASSEMBLY-567) Version wildcard in dependencySet include does not work
Date Thu, 21 Jul 2011 07:20:43 GMT
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.1, 2.2
         Environment: Windows XP
maven 2.2.1, 3.0.3
            Reporter: Stephan Oudmaijer
            Priority: Critical


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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message