> My recommendation, do NOT create a maven module if you don't need it (I 
> think that you do not need it). 

+1. Right. I would only split my client side code into multiple maven 
modules if I want to share client side code with a different project. If 
you don't do that, then adding multiple client side maven modules only adds 
complexity without a lot of value. You can still organize your code well 
within a single "client" maven module by creating multiple *.gwt.xml files, 


-- J.

You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to