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.
After this release I'll create a 1.2 branch for bug fix and/or feature backport from trunk trunk will be for 2.0 dev and require maven 2.1. It will focus on future GWT version that will also (AFAIK) be 2.0. The version match looks like a marketing strategy, isn't it ;) Thanks for your feedback and suggestions. Nicolas 2009/4/29 nicolas de loof <[email protected]> > Hi > I just saw http://jira.codehaus.org/browse/MGWT-62 was created. I myslef > had this idea for a while. > > The benefict is that the long gwt:compile process will be executed AFTER > the test phase, so can make the build more reactive (typically on IC server) > > The side-effect is that this requires us to set prerequisite to maven 2.1 > > What do you thing about this : > > [+1] Lets go maven 2.1 ! > [ 0 ] Don't care > [ -1] Please don't ! > > Nicolas >
