Agreed. I certainly am not advocating for google to change their own build system for GWT, just that GWT be friendlier to teams that do use Maven for our own projects. As DPeters states, the biggest and most painful aspect of the new war design is the mixing of source and compiled classes. Simply having the compiled classes be a separately configured location from the source would allow those of us using Maven or any other "clean source tree" file organization build process work much smoother with GWT.
-iain On Sep 30, 2009, at 8:04 AM, D Peters wrote: > Yes. I am not suggesting that GWT change their source tree to the / > src/main type structure that Maven requires. IMHO it should be > Maven's responsibilty to be flexible to difference source tree > structures. However, the concept of "keeping the source tree clean" > is an important one that GWT's build process should subscribe to.. > Otherwise it will always be a pain in the butt when setting up your > build scripts -- whatever tool that you use... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
