maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giacomo Boccardo (JIRA)" <j...@codehaus.org>
Subject [jira] (MSHADE-162) Replacing the original artifact - Windows vs.Unix different behaviors
Date Wed, 05 Feb 2014 16:19:58 GMT

     [ https://jira.codehaus.org/browse/MSHADE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Giacomo Boccardo updated MSHADE-162:
------------------------------------

    Description: 
The following commands produce different artifacts on Windows and Linux.
As you can see the project is only a sample and it's absurd to produce twice "shadeBugSample-1.0-SNAPSHOT.jar"
but in a real project I use build-helper-maven-plugin:attach-artifact and <outputFile>
instead of <shadedClassifierName> to avoid replacing the same artifact.

I just want to point out that the configuration you can see in the sample project causes different
behaviors depending on the OS used.


Windows:

$ mvn
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT-classifier.jar

$ mvn (again without using "clean")
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT-classifier.jar
shadeBugSample-1.0-SNAPSHOT-shaded.jar



Unix:

$ mvn
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar

$ mvn (again without using "clean")
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar

  was:
The following commands produce different artifacts on Windows and Linux.
As you can see the project is only a sample and it's absurd to produce twice "shadeBugSample-1.0-SNAPSHOT.jar"
but in a real project I use build-helper-maven-plugin:attach-artifact and <outputFile>
instead of <shadedClassifierName> to avoid replacing the same artifact.

I just want to point out that those configuration causes different behaviors depending on
the OS used.


Windows:

$ mvn
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT-classifier.jar

$ mvn (again without using "clean")
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT-classifier.jar
shadeBugSample-1.0-SNAPSHOT-shaded.jar



Unix:

$ mvn
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar

$ mvn (again without using "clean")
original-shadeBugSample-1.0-SNAPSHOT.jar
shadeBugSample-1.0-SNAPSHOT.jar


> Replacing the original artifact - Windows vs.Unix different behaviors
> ---------------------------------------------------------------------
>
>                 Key: MSHADE-162
>                 URL: https://jira.codehaus.org/browse/MSHADE-162
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: Windows (8) vs Unix
>            Reporter: Giacomo Boccardo
>         Attachments: shadeBugSample.zip
>
>
> The following commands produce different artifacts on Windows and Linux.
> As you can see the project is only a sample and it's absurd to produce twice "shadeBugSample-1.0-SNAPSHOT.jar"
but in a real project I use build-helper-maven-plugin:attach-artifact and <outputFile>
instead of <shadedClassifierName> to avoid replacing the same artifact.
> I just want to point out that the configuration you can see in the sample project causes
different behaviors depending on the OS used.
> Windows:
> $ mvn
> original-shadeBugSample-1.0-SNAPSHOT.jar
> shadeBugSample-1.0-SNAPSHOT.jar
> shadeBugSample-1.0-SNAPSHOT-classifier.jar
> $ mvn (again without using "clean")
> original-shadeBugSample-1.0-SNAPSHOT.jar
> shadeBugSample-1.0-SNAPSHOT.jar
> shadeBugSample-1.0-SNAPSHOT-classifier.jar
> shadeBugSample-1.0-SNAPSHOT-shaded.jar
> Unix:
> $ mvn
> original-shadeBugSample-1.0-SNAPSHOT.jar
> shadeBugSample-1.0-SNAPSHOT.jar
> $ mvn (again without using "clean")
> original-shadeBugSample-1.0-SNAPSHOT.jar
> shadeBugSample-1.0-SNAPSHOT.jar



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message