Context
- A large project with multiple maven modules or a single maven module structure.
Question
- Have you finally used the multi-maven-module or single-maven-module structure?
More details
If you worked on a large project with a long development time and contained many functions (i.e. not a trivial project), did you decide to split the project into several maven modules or go for a single-mode approach?
For example, having a multi-module structure fails when running maven commands, such as mvn gwt: eclipse (see http://bit.ly/gs4Rmo ). I think this would work well with the design of a single GWT module. And there may be other commands, similar to those described above, that have problems with a multi-module structure.
However, a multi-module structure can benefit from faster development, i.e. if you separate the “server” from the “client” module, you can compose the business logic (server) separately and pack it into the resulting web archive. Compiling the GWT code takes about 20 seconds, so if you only modify the server package, it can save you a lot of time in the long run.
What other cases, similar to those described above, you encountered while working with a project with several modules / modules?
Thank!
source
share