You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elias Elmqvist Wulcan (JIRA)" <ji...@apache.org> on 2015/07/17 15:14:04 UTC

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

     [ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elias Elmqvist Wulcan updated MJAR-198:
---------------------------------------
    Attachment: 0.tar

Example of project reproducing the bug.

> 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
>              Labels: newbie
>         Attachments: 0.tar
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)