You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephan Oudmaijer (JIRA)" <ji...@codehaus.org> on 2011/07/21 09:20:43 UTC
[jira] Created: (MASSEMBLY-567) Version wildcard in dependencySet
include does not work
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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312462#comment-312462 ]
Dennis Lundberg commented on MASSEMBLY-567:
-------------------------------------------
What change are you referring to?
All I did was correct the documentation, so that is in sync with reality.
> 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
[jira] Issue Comment Edited: (MASSEMBLY-567) Version wildcard in
dependencySet include does not work
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284467#comment-284467 ]
Benson Margulies edited comment on MASSEMBLY-567 at 11/28/11 7:54 PM:
----------------------------------------------------------------------
As far as I can tell, the spec order has always been the following, which is what is in the doc. I just tried it (with the current snapshot) and it worked fine, with a * in version.
groupId:artifactId:type:version[:classifier]
was (Author: bmargulies):
groupId:artifactId:type:version[:classifier]
> 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: Benson Margulies
> Priority: Critical
> Fix For: 2.2.1
>
>
> 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg reopened MASSEMBLY-567:
---------------------------------------
Assignee: Dennis Lundberg (was: Benson Margulies)
> 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.2.1
>
>
> 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
[jira] Closed: (MASSEMBLY-567) Version wildcard in dependencySet
include does not work
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies closed MASSEMBLY-567.
--------------------------------------
Resolution: Not A Bug
Fix Version/s: 2.2.1
Assignee: Benson Margulies
groupId:artifactId:type:version[:classifier]
> 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: Benson Margulies
> Priority: Critical
> Fix For: 2.2.1
>
>
> 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312462#comment-312462 ]
Dennis Lundberg edited comment on MASSEMBLY-567 at 10/27/12 3:59 PM:
---------------------------------------------------------------------
What change are you referring to?
All I did was correct the documentation, so that it is in sync with reality.
was (Author: dennislundberg):
What change are you referring to?
All I did was correct the documentation, so that is in sync with reality.
> 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312460#comment-312460 ]
Benson Margulies commented on MASSEMBLY-567:
--------------------------------------------
In other words, it would seem that just broke the builds of everyone who had followed the doc. Are you sure you want to do that?
> 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312463#comment-312463 ]
Benson Margulies commented on MASSEMBLY-567:
--------------------------------------------
Dennis, could there have been two different places in the doc with two different specs? Either that, or I was apparently drunk.
> 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
[jira] Commented: (MASSEMBLY-567) Version wildcard in dependencySet
include does not work
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284466#comment-284466 ]
Benson Margulies commented on MASSEMBLY-567:
--------------------------------------------
It's not just wildcards that are broken, even putting the correct version into place manually fails.
> 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
> 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MASSEMBLY-567.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2.1)
2.4
The documentation was wrong. The correct format is:
groupId:artifactId:type[:classifier]:version
Fixed in [r1402850|http://svn.apache.org/viewvc?view=revision&revision=1402850].
> 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
[jira] (MASSEMBLY-567) Version wildcard in dependencySet include
does not work
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312460#comment-312460 ]
Benson Margulies edited comment on MASSEMBLY-567 at 10/27/12 2:38 PM:
----------------------------------------------------------------------
In other words, it would seem that this change breaks the builds of everyone who had followed the doc. Are you sure you want to do that?
was (Author: bmargulies):
In other words, it would seem that just broke the builds of everyone who had followed the doc. Are you sure you want to do that?
> 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