On Wed, Dec 10, 2008 at 11:33 AM, Charlie Collins <[EMAIL PROTECTED]> wrote: > > You don't need to do that, GWT-Maven can do it automatically. > > Are you using the "mergewebxml" goal?
this was too easy. i simply had to change the automatically generated pom.xml from the archetype: 1. removed comments at <goal>mergewebxml</goal> 2. removed comments at <webXml>target/web.xml</webXml> and "mvn install" works like a charm... saved my day! thanks for the quick response :D raphael! > > This doc page says is sort of titled wrong (it's really about more > than the embedded Tomcat) but it might help: > http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/tomcatlite.html. > > On Dec 10, 5:26 am, "Raphael André Bauer" > <[EMAIL PROTECTED]> wrote: >> hi folks, >> >> i want to do a simple thing: run something like "mvn install" and get >> a nice packaged .war containing my gwt app. >> this works. >> but. >> the problem i am facing is, that i have to set the servlet-mapping in >> the web.xml manually for every RPC point of the gwt. >> >> imho this is really double work, because the info is already somehow >> contained in the gwt.xml as "<servlet path=...". >> >> am i missing a thing, or do i have to manually add the mappings to the >> web.xml in order to get my gwt app running in a productive >> environment? >> >> thanks! >> >> raphael > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" 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/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
