Below is my speculation about the allocation of responsibilities between Maven and CC:
CC: 1) Timing - Determines when to trigger builds a) Knows when source files change using <cvs> and triggers build via <schedule><maven>. b) Knows when a dependency snapshot changes using <mavensnapshotdependency> and triggers build. 2) Mail - Mails someone for each project that fails Maven: 3) Build/Test - Peforms a build/test triggered by CC via <schedule><maven>. 4) Site - creates multiproject site after a build sequence. Now here are some questions: 1) How does CC automatically learn about the dependencies in my project.xml so that it can fulfill responsibility 1b. 2) How does CC automatically learn about the nag e-mail address in my project.xml so that it can fulfill responsibility 2. 3) How does CC know if a Maven build fails so that it can fulfill responsibility 3. 4) How does CC trigger Maven multiptoject:site and site:deploy _after_ all the builds are done. Thanks again. -Doug --- Erik Husby <[EMAIL PROTECTED]> wrote: > Do > > >Here is what I am guessing: > > > >1) CC should invoke Maven instead of > vice > >versa, because CC knows when projects > have > >changed. > > > > > > > I am not a CC expert, but CC > 2.2 can directly > invoke Maven. I've just started experimenting with > this. > > >2) Maven should create the CC > configuration > >files using the CC plugin. > > > > > > > There is a Maven plugin for this -- but I have no > direct experience with it. > > >Here are my big questions: > > > >1) Is what I'm suggesting correct? > > > > > > > Yes > > >2) If not, what is a better arrangement between > Maven > >and CC. > > > >3) How do I set this up? > > > > > > > Well, I started by reading the CC > documentation and starting > with a simple project. So Far So Good. Have not > gotten the CC > maven dependency check to work but right now > CC has moved to > the bottom of the todo list. > > >4) Can anyone provide somewhat complete example > files > >or documentation for doing this? > > > > > > > Check the CC documenation and ask > questions on their > wiki/mailing list. > http://cruisecontrol.sourceforge.net/ > > -- > Erik Husby > Team Lead for Software Quality Automation > Broad Institute of MIT and Harvard > Rm. 2192 320 Charles St > Cambridge, MA 02141-2023 > mobile: 781.354.6669, office: 617.258.9227, > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
