[
https://jira.codehaus.org/browse/MSHADE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363028#comment-363028
]
Christopher Currie commented on MSHADE-126:
-------------------------------------------
Is it possible to have the shade plugin automatically instruct the jar plugin
to set forceCreation=true for this case?
> Running shade twice without clean leads to warnings and errors
> --------------------------------------------------------------
>
> Key: MSHADE-126
> URL: https://jira.codehaus.org/browse/MSHADE-126
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)