Maybe some good 'how to use Maven to enable common development practices' section:
*Why use CI? *How to use CI in Maven: --with CruiseControl --with Anthill --with XXXX *Why use SCM? *How to use SCM in Maven: --with CVS --with subversion --with XXXXX *Why use Unit Testing? *How to use unit testing in Maven: --with Junit --with Cactus *Why use Code Coverage? *How to use code coverage in Maven: --with Clover --with Jcoverage --with Emma *When, Why, and How to use multiproject/reactor/etc? And so on and so forth. Maybe this book should offer a pre-built ready-to-roll project that uses different enablers to do the same thing, ala: cruisecontrol-cvs-junit-clover suite and an anthill-subversion-junit-emma suite. One of the difficult things is that Maven is *so* powerful and flexible, sometimes get lost on how to get the pieces to work together. Couple of quick coppers, -D --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
