What I do is calling the site goal first, then turn off unit testing (and Clover) and run the deploy goals. That way the unit tests are not being run twice and I have clean (non-Clovered) jars in my remote repository.
You need to do some jelly scripting including this line: <j:set var="maven.test.skip" value="true"/> to disable running the tests On 4/14/05, David Jackman <[EMAIL PROTECTED]> wrote: > I'm trying to set up a continuous build (using cruise control) that will > deploy the target artifact for each subproject, build the website for > each subproject, create a single website for the multiproject, then > deploy the single website. > > I can easily have cruise control execute the multiproject:deploy goal to > build & deploy all the artifacts, followed by the multiproject:site goal > to build & merge the subproject web sites, followed by the site:deploy > goal to deploy the main website (the docs say multiproject:site-deploy > would do this, but it doesn't work). > > However, the multiproject:site goal will want to build all of the > artifacts again, doing many things that were already done with the > multiproject:deploy goal. Is there a more efficient way to do this? > > ..David.. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
