No, I do all with Maven (and some pieces with ANT inside Maven)... I have a scalable Spring/Hibernate backend and several GWT front ends that connect to the same backend. That's why I use my own SerializationPolicy solution as the GWT *.gwt.rpc file solution works very poor in these kind of noserver environments. You might want to read this post: http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/600aa2f851f33606/16c24bb26c680a9d?lnk=gst&q=gwt+policy#16c24bb26c680a9d
And the related issue in the issue tracker (you might want to vote it to follow it): http://code.google.com/p/google-web-toolkit/issues/detail?id=4701 I use GWT-RPC mechanism which works pretty well. See the presentation about some tips about that. The maven plugin that I use: http://mojo.codehaus.org/gwt-maven-plugin/ I would surely use that one. It works very well and is very active. (I used another one before) Ed -- 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.
