Hi
I'm looking into http://jira.codehaus.org/browse/MSHARED-131 which
triggered the question in the subject. Maven Archiver and Maven WAR
Plugin, and I'm guessing the Dependency Plugin as well, treats a
non-existing classifier (classifier == null) differently to an empty
classifier (classifier == "").
All the examples above, are about creating a suitable file name for a
given artifact. MSHARED-131 claims that Maven Archiver is broken because
of the behavior below.
For this artifact:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<classifier></classifier>
</dependency>
it produces a file name for the artifact that looks like this:
junit-3.8.1-.jar
If the classifier element is removed it produces this file name:
junit-3.8.1.jar
What is the correct way to handle this?
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
