Hi Darren, > -----Original Message----- > From: Darren Hartford [mailto:[EMAIL PROTECTED] > Sent: mercredi 8 juin 2005 22:22 > To: Maven Users List > Subject: RE: [Mavenbook.org] What content would you like to see? > > 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?
Shouldn't all these questions rather be added to the maven.apache.org's web site FAQ? > 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. I guess I wasn't clear. The book is already written (it was finished in April 2005). It's currently being printed and will be available in book shops around the 20th of June. You can browse the TOC here: http://www.oreilly.com/catalog/mavenadn/index.html The book covers continuous integration with Maven by demonstrating it with CruiseControl. We use Subversion for our examples. The book's source code is freely available under an Apache license at http://mavenbook.xwiki.com/xwiki/bin/view/Main/Source > 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. I agree. I hope the book will be useful in that regards. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
