[
https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957284#comment-17957284
]
Matthias Bünger commented on MJAR-198:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#356|https://github.com/apache/maven-jar-plugin/issues/356].
> jar:jar without classifier replaces default jar
> -----------------------------------------------
>
> Key: MJAR-198
> URL: https://issues.apache.org/jira/browse/MJAR-198
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6
> Environment: Windows 8.1 Pro
> JDK 1.8 45
> Maven 3.2.5
> Reporter: Elias Elmqvist Wulcan
> Assignee: Karl Heinz Marbaise
> Priority: Minor
> Labels: newbie
> Fix For: 3.0.0
>
> Attachments: 0.tar, mvn.install.debug.txt
>
>
> 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|https://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#classifier]
> 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]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
