[
https://jira.codehaus.org/browse/MSHADE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307562#comment-307562
]
Benson Margulies commented on MSHADE-126:
-----------------------------------------
A real fix to this is a big job. To comprehensively fix this, you'd need:
# shade to keep the pre-shaded jar around under some name
# shade to detect when there's a good reason to rebuild the pre-shaded jar,
including changes to dependencies.
Without all this, changing the config of the jar plugin is the best thing.
> 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
