nicolas de loof <nico...@apache.org> writes:

> As Paul suggested, I've created a 2.0 version in Jira. 
>
> 1.1 will be 2.0.9 compatible as 1.0 was, and focus on plugin merge +
> GWT 1.6 support.   We still have to fix the docs and sample (and any
> bug early adopters may repport), but we are near a 1.1 release. Maven
> 2.1 user will have to configure an <execution> but this is an
> acceptable workaround for backward compatibility.

I'm just in the process of moving my team from gwt-maven.googlecode.com
over to the Codehaus' gwt-maven-plugin. We're still using Maven 2.0.x on
all our projects (a couple of dozens, different teams), so forcing some
teams to upgrade to Maven 2.1.x seemed like a step too big for the
moment, although I haven't experienced any issues myself yet.

So, delaying MGWT-62 to future major release 2.0 appeals to me. Having
an extra execution-configuration doesn't seem like a drawback to big for
Maven 2.1.x users - IMHO.

+1

-Stefan


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to