I've run into this exact same problem. I haven't tried too hard to fix it yet. It hasn't cropped up much since our web.xml changes so infrequently. I'm currently only working with 2 other developers, so it also hasn't been an issue to have everyone just know that they need to re-copy this file if it changes or if they do a super-clean build (including wiping out the war/ directory, which I will eventually attach to the clean lifecycle in maven, but only after figuring out this problem).
My best lead is this page in the gwt-maven-plugin docs: http://mojo.codehaus.org/gwt-maven-plugin/user-guide/war-folder.html I want to go with solution 1 on that page, but I'm wary of inline deployments... it depends on how granular the svn:ignore settings would have to be. I also don't completely understand the claimed benefit of using different web.xml deployment descriptors for hosted mode vs. real web application. Looking just now, however, I'm noticing that the documentation has been updated recently, seemingly related to the 1.2-SNAPSHOT version of the plugin with preliminary GWT 2.0 support. Specifically, this looks like it could be helpful: http://mojo.codehaus.org/gwt-maven-plugin/user-guide/hosted.html I'll post anything I find here if I have time to take another look at this and find out anything useful. -Brian On Oct 6, 2:07 pm, ATom <[email protected]> wrote: > Nobody know solution? It's only way use mavent ant plugin? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
