[
http://jira.codehaus.org/browse/MSHADE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116228
]
Daniel Kulp commented on MSHADE-5:
----------------------------------
I have no way of testing this (no windows boxes), but looking at the code, we
never called jarFile.close on the jars we were reading. Thus, the file was
probably locked. I fixed that. I'd appreciate it if you could see if that
helps.
> 50% of the time I 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