Thank you Thomas and Colin for your replies. Thomas, sorry for posting in the wrong place. I didn't even know there is a gwt-maven-plugin users group... thanks for pointing that out!
Working with separated projects with GWT, Maven, Eclipse (and his friends - the plugins!) and App Engine is really hard and sometimes frustrating... but when it works is really useful, mainly for environments with continuous integration. All hail to The Maven Way™! On Sunday, February 9, 2014 4:19:20 PM UTC-2, Thomas Broyer wrote: > > AFAICT, the warning originally was added because gwt-dev bundles various > dependencies, such as Xalan and Xerces, ECJ, Apache Commons, Jetty, etc. > that could conflict with dependencies you use for your server-side code. > That said, using the same project for client and server sides is a bad > idea, and violates The Maven Way™, so in practice gwt-dev should > effectively not be a problem. FWIW, I do believe that warning should be > removed. > > Also, BTW, you should have rather posted to the gwt-maven-plugin users > group, or the GWT users group. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
