I have my doubts...
I don't know the amount of time it usualy takes before GWT comes with a new release, but if this takes too long, we might run into some trouble. What if we have bugfixes and new features on a already released version? Suppose we have GWT-2.1 and the gwt-m-p-2.1, should the fixed version be gwt-m-p-2.1.1? Gotcha!, because a week later GWT also discovered some serious issues and releases a 2.1.1 as well. Now both versions are out of sync again. It might sounds logic, but I think it would only work if GWT itself releases the maven plugin as part of a suite. Although the versions are pretty close to each other, I wouldn't try to follow the GWT-version. - Robert > From: [email protected] > Date: Mon, 30 Aug 2010 21:59:16 +0200 > To: [email protected] > Subject: Re: [mojo-dev] [Vote] [gwt] align gwt-maven releases with GWT ones > > +1 > > 2010/8/30 nicolas de loof <[email protected]>: > > Hi, > > With many API and options changes between GWT releases, the plugin gets more > > complex any time Google guys release a new SDK version. I'd like to change > > the plugin design to "align" gwt-maven to a GWT sdk release. > > The planned action are : > > > > Move trunk to a new "1.3" branch (if someone wants to support it and fix > > bugs) > > Start changes in trunk as "2.1", to be released when GWT 2.1 is final. > > Remove all dynamic artifact resolution depending on requested GWT version > > Remove support for older releases of the SDK > > Add explicit dependency on GWT 2.1 artifacts > > Support only GWT 2.1 features > > > > [ ] +1 let's do that > > [ ] 0 don't care > > [ ] -1 Please don't do that, because ... > > Nicolas > > Nicolas > > > > -- > Olivier > http://twitter.com/olamy > http://fr.linkedin.com/in/olamy > http://www.viadeo.com/fr/profile/olivier.lamy7 > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > >
