[MJAR-198] jar:jar without classifier replaces default jar

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.3.1, 2.3.2, 2.4, 2.5, 2.6
• Fix Version/s: 3.0.0
• Labels: newbie
• Environment: Windows 8.1 Pro; JDK 1.8 45; Maven 3.2.5
• Assignee: Karl Heinz Marbaise
• Reporter: Elias Elmqvist Wulcan
• Created: 17/Jul/15 13:12
• Updated: 20/Nov/18 21:11
• Resolved: 19/Dec/15 21:47

Description

If I add an execution of jar:jar in a project of packaging jar and do not configure a classifier for the additional jar, the additional jar will be installed instead of the default jar.

Omitting a classifier in the configuration for the goal jar:jar is documented to have the effect that the jar will not be attached and this is the behavior that I want. Instead, the jar is attached and replaces the default jar.

AbstractJarMojo.java:254 checks nullness of classifier to decide whether to attach or not. JarMojo.java:51 declares a default value the empty string for classifier. Maybe the combination of these lines cause the bug.
http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111&view=markup
http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111&view=markup

Issue Links

• causes: MJAR-253 Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.
• relates to: MJAR-254 The fix for MJAR-198 is incomplete: filename conflict not detected