[
https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065561#comment-15065561
]
Hudson commented on MJAR-198:
-----------------------------
SUCCESS: Integrated in maven-plugins #4902 (See
[https://builds.apache.org/job/maven-plugins/4902/])
[MJAR-198] jar:jar without classifier replaces default jar
The maven-jar-plugin now will fail if you try to replace the original
artifact in case of a second execution without defining a classifier.
Improved documentation about the classifier. (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev&rev=1720976])
* maven-jar-plugin/src/it/MJAR-198
* maven-jar-plugin/src/it/MJAR-198/invoker.properties
* maven-jar-plugin/src/it/MJAR-198/pom.xml
* maven-jar-plugin/src/it/MJAR-198/src
* maven-jar-plugin/src/it/MJAR-198/src/main
* maven-jar-plugin/src/it/MJAR-198/src/main/java
* maven-jar-plugin/src/it/MJAR-198/src/main/java/A.java
*
maven-jar-plugin/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java
* maven-jar-plugin/src/main/java/org/apache/maven/plugins/jar/JarMojo.java
> jar:jar without classifier replaces default jar
> -----------------------------------------------
>
> Key: MJAR-198
> URL: https://issues.apache.org/jira/browse/MJAR-198
> Project: Maven JAR Plugin
> 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 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
(v6.3.4#6332)