I like this. On Fri, Jun 29, 2012 at 9:48 AM, Stephen Connolly <[email protected]> wrote: > 3) add a shade:clean goal which removes the jar and let people bind > that to prepare-package > > On 29 June 2012 14:28, Benson Margulies <[email protected]> wrote: >> OK, now I understand this. >> >> The jar plugin will optimize out writing a jar in some cases. >> >> This is never a good idea is shade has produced the jar. But the jar >> plugin has no way, I can see, to notice this. So the jar plugin leaves >> the shaded jar and then shade explodes. >> >> I can see two possible approaches: >> >> 1) Write notes in both plugin's doc to explain what is going on. I >> will certainly add some doc to the jar plugin, since the existing >> explanation of the forceUpdate param is not helpful. >> >> 2) Make the jar plugin look for some sort of time that the shade >> plugin can leave lying about to indicate that the jar has been >> tampered with and must be rebuilt. >> >> Thoughts? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
