> The one remaining issue is the new build output format (WAR), and how > resources are deployed. I'm totally against having GWT compile > directly into /src/main/webapp. It's completely against the principles > of keeping your source tree clean and putting all artifacts under > target. If you stick with traditional maven approach, it means you > need to execute war:exploded first before launching hosted mode (and > again if you want to change something without restarting the hosted > mode).
I totally agree here. The "old" GWt build proceding was naive and we needed twirks to get it running. When I first heard of the new structure I was really happy: GWT is growing up! But than I had a closer look at it and I could not believe it! How can the GWT developer be so genious and so naive at the same time??? How could they miss that point? Don't they use their own dog food? Did they never see how projects are build outside? Or do they use something we don't know? It is hard to argue to get resources/ time/ budget for a build infrastructure change. We need budget now, because GWT 1.6 does it differently - and you know what? It is naive again! We will need budget again! We will probably need to wait for GWT 1.7, GWT 1.8, GWT 1.9, GWT 2.0 to have this issue fixed. I can't tell how disappointed I am. brgds, P.G.Taboada --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
