Re: Shade plugin non backward compatible change

2012-06-27 Thread Benson Margulies
On Wed, Jun 27, 2012 at 7:39 AM, Olivier Lamy wrote: > +1 > fine for me OK, 1.7.1 staged and out for vote. > > 2012/6/27 Benson Margulies : >> Here's my proposed plan. >> >> 1) I do something about MSHADE-123: move the default back to basedir. >> >> 2) I release 1.7.1. >> >> 3) You move the next

Re: Shade plugin non backward compatible change

2012-06-27 Thread Olivier Lamy
+1 fine for me 2012/6/27 Benson Margulies : > Here's my proposed plan. > > 1) I do something about MSHADE-123: move the default back to basedir. > > 2) I release 1.7.1. > > 3) You move the next version to 2.0 or 3.0, and fix MSHADE-112. > > 4) I apply the patch to MSHADE-103 that requires us to de

Re: Shade plugin non backward compatible change

2012-06-26 Thread Benson Margulies
Here's my proposed plan. 1) I do something about MSHADE-123: move the default back to basedir. 2) I release 1.7.1. 3) You move the next version to 2.0 or 3.0, and fix MSHADE-112. 4) I apply the patch to MSHADE-103 that requires us to depend on Maven 3. 5) anyone who really wants a fix for Mave

Shade plugin non backward compatible change

2012-06-26 Thread Olivier Lamy
Hi, I don't know if you have a look @ MSHADE-112 Basically the goal is to be able to pass more and more parameters to the Shader. This need to change -void shade( Set jars, File uberJar, List filters, List relocators, -List resourceTransformers ) +void shade( ShadeRequest