I think both choices are fine. The risk-averse users on Maven 2.2.1 are 
probably also not on Java 7 :) Put the other way, requiring a bump to Maven 3 
to build plugins on Java 7 sounds reasonable to me.

On 24/09/2012, at 6:56 AM, Dennis Lundberg <[email protected]> wrote:

> Hi
> 
> We have other developers to think about as well. Even though might be OK
> with requiring Maven 3 to build our plugins, the plugin testing stuff is
> used by many other plugins. Since they might not be OK with it, I think
> we should do a 1.3 release.
> 
> On 2012-09-23 22:44, Kristian Rosenvold 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]
>> 
> 
> 
> -- 
> Dennis Lundberg
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

--
Brett Porter
[email protected]
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to