[ 
https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633112#comment-14633112
 ] 

Elias Elmqvist Wulcan commented on MJAR-198:
--------------------------------------------

That is very nice but the artifact is still attached and installed which is 
opposite of what the documentation says.

{quote}
classifier
String
Classifier to add to the artifact generated. If given, the artifact will be 
attached. _If this is not given,it will merely be written to the output 
directory according to the finalName._
{quote}

A project using jar packaging and also building some intermediary jar files, 
will have its default jar overwritten by one of the intermediary jar files on 
install. If the intermediary jars are strange in some way, for example with 
special class path prefixes or special excludes, this behavior will cause 
depending projects to fail.


> 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
>            Priority: Minor
>              Labels: newbie
>         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)

Reply via email to