If that is the only reason for the release and it can be fixed in an earlier release, then I see no reason not too.
This is also in line with the general Maven ethos of not forcing people to upgrade. -Chris Sent from my iPhone On 24/09/2012, at 6:44 AM, Kristian Rosenvold <[email protected]> wrote: > At the moment, most of the plugin it's don't run under java 7 (dont > know about 1.6). > > The reasons for this seems to be largely that the version of easymock > that is used in all released versions of plugin-testing > is incompatible with java 7. And since it's easymock classextension, > it looks like upgrading has to be painstakingly > synchronized between plugin-testing and the client (you can't just > override in "maven-assembly-plugin") > > Now version 2.0 of plugin-testing was released which required maven 3 > to build. Right now I'm considering releasing > 2.1 to fix the easymock "situation", but I'm also contemplating > releasing 1.3 instead to fix the easymock situation there. > > The thing is, if I only fix this in 2.1 I will effectively force about > half our plugins to require maven 3 to build. How much of an issue > will this be wrt maintaining 2.2.1 comptaibility ? > > I would very much appreciate your .02 euros on this one ;) > > Kristian > > --------------------------------------------------------------------- > 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]
