On Tue, Feb 18, 2014 at 3:22 PM, Thomas Broyer <firstname.lastname@example.org> wrote:
> (the "instead of" bit depends on your project; I keep thinking that if you
> mix client-side and server-side code in the same Maven module, then you're
> doing it wrong; Maven wants you to modularize your project, and it really
> works great; see https://github.com/tbroyer/gwt-maven-archetypes for
Hello Thomas (and list), I'm thinking to "split" my current GWT in
some "submodules" also to avoid the problem in thread (actually we
have GWT 2.5.1).
I see the example in , but it focus on multi-maven modules on the
"client-side", do you know if there are any other example/best
practices for client/server code splitting?
Luca Morettoni <luca(AT)morettoni.net> | http://www.morettoni.net
http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni
Google+ profile: https://www.google.com/+LucaMorettoni
Member of GDG Perugia: http://perugia.gtugs.org
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.