On Friday, May 30, 2014 3:49:15 PM UTC+2, Luca Morettoni wrote: > > On Tue, Feb 18, 2014 at 3:22 PM, Thomas Broyer wrote: > > Yes. > > (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 > > examples) > > 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 [1], 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? >
The link you just quoted above: https://github.com/tbroyer/gwt-maven-archetypes ;-) -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
