[
https://jira.codehaus.org/browse/MSHADE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MSHADE-126:
------------------------------------
Description:
Frequently, when I run a build without 'clean', I get a torrent of unwanted
'duplicate symbol' errors from shade. More recently, when I did the same for a
build that includes some shading that combines files from META-INF, this turned
into a fatal error.
I've managed to produce a repro with maven 3.0.4. Just run 'mvn install' twice
in a row to reproduce this. The impression it gives is that, somehow, the
shaded jar from the previous build is used as the input, instead of a new jar
built from scratch this time around.
was:
Frequently, when I run a build without 'clean', I get a torrent of unwanted
'duplicate symbol' errors from shade. More recently, when I did the same for a
build that includes some shading that combines files from META-INF, this turned
into a fatal error.
I've never had a repro, but I'm opening this JIRA as a goad to myself to come
up with one and attach it here.
Testcase included: yes
> Running shade twice without clean leads to warnings and errors
> --------------------------------------------------------------
>
> Key: MSHADE-126
> URL: https://jira.codehaus.org/browse/MSHADE-126
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.7.1
> Reporter: Benson Margulies
> Attachments: epom.xml, shade.boom.log, shade-error.tgz
>
>
> Frequently, when I run a build without 'clean', I get a torrent of unwanted
> 'duplicate symbol' errors from shade. More recently, when I did the same for
> a build that includes some shading that combines files from META-INF, this
> turned into a fatal error.
> I've managed to produce a repro with maven 3.0.4. Just run 'mvn install'
> twice in a row to reproduce this. The impression it gives is that, somehow,
> the shaded jar from the previous build is used as the input, instead of a new
> jar built from scratch this time around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
