gwt multi-module vs single-module project

Question

I've seen the GWT Expenses app from GWT SDK is using single module structure.

Is this a best practice? Are there any cons in having the project split into multiple maven modules, i.e:

• client
• shared
• server

Answer 1

The GWT compiler and DevMode don't really care about how you structure your build system as long as all of the client and shared resources are available on the GWT classpath and the server components have been compiled into the webapp's WEB-INF/classes directory (or lib/foo.jar) if you're using DevMode's built-in Jetty server.