You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/12/11 08:57:57 UTC

[jira] Updated: (MSHADE-5) Whenever I do a deploy and run the shade plugin, it's unable to replace the original jar

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

Dan Fabulich updated MSHADE-5:
------------------------------

    Priority: Blocker  (was: Major)
     Summary: Whenever I do a deploy and run the shade plugin, it's unable to replace the original jar  (was: 5% of the time I run the shade plugin, it's unable to replace the original jar)

I just discovered that this problem occurs every time I try to deploy a snapshot that uses shade!  This is a blocker after all.

> Whenever I do a deploy and run the shade plugin, it's unable to replace the original jar
> ----------------------------------------------------------------------------------------
>
>                 Key: MSHADE-5
>                 URL: http://jira.codehaus.org/browse/MSHADE-5
>             Project: Maven 2.x Shade Plugin
>          Issue Type: Bug
>         Environment: Windows XP SP2, Java 1.5.0_12
>            Reporter: Dan Fabulich
>            Priority: Blocker
>
> I tried to wire up the shade plugin in surefire trunk.  About 50% of the time I run the shade plugin I get a "[WARNING] Could not replace original artifact with shaded artifact!"  IMO that should halt the build, because it goes on to use the stripped POM without using the shaded jar; hilarity ensues.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira