title: Structure for big GWT project
body: <h2>Context</h2>
  
  <ul>
  <li>big project with multi maven module or single maven module structure</li>
  </ul>
  
  <h2>Question</h2>
  
  <ul>
  <li>did you finally use multi-maven-module or single-maven-module structure?</li>
  </ul>
  
  <h2>Details</h2>
  
  <p>If you've worked on a big project that had long development duration and contains lots of functionality(i.e. not a trivial project), did you choose to split the project into multiple maven modules or went with the single-module approach?</p>
  
  <p>For example, having a multi-module structure, crashes when running maven commands like mvn gwt:eclipse(see <a href="http://bit.ly/gs4Rmo" rel="nofollow">http://bit.ly/gs4Rmo</a>). I guess this would have worked well with single module GWT project. And there could be other commands like the above that has issues with multi-module structure.</p>
  
  <p>However, the multi-module structure could bring the benefits of a faster development, i.e. if you separate the "server" from "client" module, you could compile the business logic(server) separately and package it into resulting web archive. Compiling the GWT code, takes about 20 seconds, so if you only modify the server package, it could save you lots of time in the long run. </p>
  
  <p>Which other cases like the one above did you encounter when working with a multi-module/single module project?</p>
  
  <p>Thank you!</p>