Re: [assembly] Empty classifier in dependency causes extra dash

2011-12-14 Thread Antonio Petrelli
2011/12/14 Stephen Connolly > assembly should have the fix anyway, or else the minimum version of maven > that it supports would need to be supped to the first maven version with > the fix > Ok I created the issue: http://jira.codehaus.org/browse/MASSEMBLY-591 I attached a simple test case too.

Re: [assembly] Empty classifier in dependency causes extra dash

2011-12-14 Thread Stephen Connolly
assembly should have the fix anyway, or else the minimum version of maven that it supports would need to be supped to the first maven version with the fix - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using s

Re: [assembly] Empty classifier in dependency causes extra dash

2011-12-14 Thread Antonio Petrelli
2011/12/14 Stephen Connolly > Smells like a bug... > > Yes it does. However I debugged the process and noticed that the "getClassifier" of org.apache.maven.artifact.Artifact class contains an emtpy String. This is the reason why I cannot decide if it is a Maven bug (not treating empty classifier

Re: [assembly] Empty classifier in dependency causes extra dash

2011-12-14 Thread Stephen Connolly
Smells like a bug... On 14 December 2011 12:42, Antonio Petrelli wrote: > Hi all > I am writing here since I don't know if it is a bug, and if yes, if it is a > bug of Maven core or the assembly plugin. > I am using assembly plugin version 2.2.2 and 2.2.3-SNAPSHOT compiled from > source. > When I

[assembly] Empty classifier in dependency causes extra dash

2011-12-14 Thread Antonio Petrelli
Hi all I am writing here since I don't know if it is a bug, and if yes, if it is a bug of Maven core or the assembly plugin. I am using assembly plugin version 2.2.2 and 2.2.3-SNAPSHOT compiled from source. When I add a dependency of this type (notice the empty classifier element): [snip]