+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 -~----------~----~----~----~------~----~------~--~---
