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
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.