Re: what is the best practice for handling build output, reports and archives?

2007-03-26 Thread Erik Drolshammer
Rémy Sanlaville wrote: btw, continuum-1.1-alpha is on its way. It has a lot of additional features compared with 1.0.3. I am trying to find some documentation on continuum-1.1 and the additional features. Do you have some links ? No, good ones, but you can try; http://jira.codehaus.org/secu

Re: what is the best practice for handling build output, reports and archives?

2007-03-26 Thread Rémy Sanlaville
Why not use Continuum [1]? Continuum is designed to build Maven-projects.. If you modify the site-configuration a bit Continuum should do what you want pretty much out of the box if you can set up apache to serve the generated output. btw, continuum-1.1-alpha is on its way. It has a lot of addit

Re: what is the best practice for handling build output, reports and archives?

2007-03-26 Thread Erik Drolshammer
Baz wrote: All, What is the best practice for handling build outputs, reports and archives? Here are the brief environments: 1. Build scheduling systerm such as CruiseControl. 2. Maven 2.0. 3. #1 and #2 running nightly, continuous and ad-hoc builds. Outputs: 1. Build tree. 2. Build outputs. 3

what is the best practice for handling build output, reports and archives?

2007-03-25 Thread Baz
All, What is the best practice for handling build outputs, reports and archives? Here are the brief environments: 1. Build scheduling systerm such as CruiseControl. 2. Maven 2.0. 3. #1 and #2 running nightly, continuous and ad-hoc builds. Outputs: 1. Build tree. 2. Build outputs. 3. Junit outp