On Sat, Apr 27, 2013 at 5:03 AM, zhu19774279 <[email protected]> wrote: > For example, I have a SSH project, how many modules should I split? A > service-module, a DAO-module, a action-module and a web-app module? Are > there any guidelines or rules I should follow?
Splitting at your layers' and/or components' boundaries really help following your architecture (whichever it is: traditional layered architecture, onion architecture, etc.) If you haven't settled on a particular architecture, then do not try to split too early; over time, an architecture will emerge and you can then split, provided it adds value to your project/team (“premature optimization” also applies to the developer workflow) I otherwise agree with Ron, it's not specific to Maven, neither actually even specific to Java. -- Thomas Broyer /tɔ.ma.bʁwa.je/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
