|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Richard Eggert (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Richard Eggert (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Steven Bethard (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Steven Bethard (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... Steven Bethard (JIRA)
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... JIRA
- [mojo-dev] [jira] (MVERSIONS-163) includes/exclude... JIRA

The description of this issue covers a bunch of stuff (the includes/includesList confusion, shell escaping, etc.). I assume that when you say "the classifier bug that this issue is about", you mean the second paragraph from Stephen Wiebe's second comment:
And to that, yes, I can also confirm that 4-part coordinates (groupId:artifactId:type:version) work but 5-part coordinates (groupId:artifactId:type:classifier:version) don't in 1.3.1.