You can stay with original maven structure, src/main/webapp directory including and still use GWT as before. Also GEP plugin is capable of working with it. You have to follow the wiki instruction on codehause GWT plugin - http://mojo.codehaus.org/gwt-maven-plugin/user-guide/war-folder.html. + you have to redirect the output of web.xml in war-plugin also to the war directory and then everything works fluently.
On Sep 30, 8:46 am, Michał Sędzielewski <m.sedzielew...@gmail.com> wrote: > and what is the opinion of Googlers? > > On 29 Wrz, 20:37, Daniel Jue <teamp...@gmail.com> wrote: > > > +1 for Maven nested module friendliness. > > > On Tue, Sep 29, 2009 at 12:25 PM, Iain Shigeoka <iain.shige...@gmail.com> > > wrote: > > > > +1 Maven friendly is ideal. Less ideal but better than current is > > > separation of source and compiled code as the original poster mentioned. > > > > -iain > > > > On Sep 29, 2009, at 9:02 AM, Michał Sędzielewski wrote: > > > >> I agree, it would be nice to have maven structure in GWT 2.0 > > > >> On 28 Wrz, 15:45, logicpeters <logicpet...@gmail.com> wrote: > > >>> Can anyone tell me if there are plans to rework the way the > > >>> currentGWTproject structure is configured for2.0? Mxing the source > > >>> and > > >>> compiled code in the /war folder has been a real pain in the butt for > > >>> build scripts and source control. I've been trying to "mavenize" our > > >>> project, and find the various solutions to be un-elegant hacks that > > >>> wind up confusing the structure even more. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
