You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "J.Cranendonk (JIRA)" <ji...@apache.org> on 2018/06/19 08:06:00 UTC

[jira] [Commented] (MJAR-198) jar:jar without classifier replaces default jar

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

J.Cranendonk commented on MJAR-198:
-----------------------------------

Was an issue made for the comment Archie Cobbs mentioned?

We have the same issue, broken build with multiple jar plugins configurations with different finalName's.

I'm whitelisted, so can't reach the user or dev list, and google sends me here regarding this issue.

What is the workaround? Adding classifier modifies the final name of the jar, instead of just using finalName, it becomes finalName-classifier..

 

> 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
(v7.6.3#76005)