I'm curious how folks are adapting to this new layout. How many of you are letting GWT write its output to war/**, and how many are going the maven approach and moving things to target/war/** ? Personally, I much prefer the maven idea of keeping source and generated files separate. However, I don't want to be continually swimming upstream against this layout, in particular if it will cause pain for my colleagues using Eclipse (I'm an Intellij user myself).
Thanks. K On Apr 16, 2:00 pm, Matt Bishop <[email protected]> wrote: > One of the big wins withMavenis the "rigid" directory structure, > where source files of all stripes are in src/ and build outputs are in > target/. It's good practice because it doesn't allow for intermingling > source files and build files. > > The new GWT war/ dir next to src/ problematic because you have to be > careful how you clean up. I can see many an "aaargh!" being screamed > out in the early morning hours when a tired developer discovers a bug > in her ant script, or when he trashes the war/ dir accidentally. > > I would much rather have seen src/java and src/war (better yet, src/ > webapp) and the HostedMode compiler would copy src/webapp to war/ > before compilation. It would be a whole lot safer and wouldn't really > cost that much, even for large projects with a whole lotta webapp/** --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
