Thanks for response. That's similat what I have in place, and I am using luntbuild:
mvn clean install (on success: post build ) mvn deploy site site:deply But the problem is that now I have to run unit tests multiple times. My unit tests run for around 15 minutes. That brings the total build time to 1 hour. This also doubles disk usage in the local repository on the build machine because the install phase is invoked twice. There should be a more elegant way to do this than this ( IMO ) hack. Thanks, -Moiz -----Original Message----- From: Max Cooper [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 2:08 PM To: Maven Users List Subject: Re: Consistency of deployed modules Run maven twice: mvn clean install if (success) mvn deploy Build server software like Luntbuild can automate this for you. -Max [EMAIL PROTECTED] wrote: > I have a multi-project build. I run a "mvn clean deploy" build every > night. Sometimes the builds fail with one of the modules and I end up > with an inconsistent set of deployed modules. How can I delay the > deployment of the modules so that the deploy happens only when all of > the modules have sucessfully completed the install phase of the > life-cycle. This way, I always have a consistent set of modules. > > Thanks > > -Moiz > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
