Thanks for the feedback. Definitely good to know others are in the same boat, and I definitely never would've thought of the scm bootstrapping solution.
Thanks, Baron -----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Fri 7/21/2006 8:49 PM To: [email protected] Subject: Re: Release strategy with Continuum and if http://jira.codehaus.org/browse/MRELEASE-100 implemented than all you need is mvn release:release -D On 7/21/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > We build official releases "manually". But Dan's suggestion seems > reasonable. > > Wayne > > On 7/21/06, dan tran <[EMAIL PROTECTED]> wrote: > > you can add a build defintion to you current project that do this. > > > > mvn scm:bootstrap -Dgoals="-B,release:prepare,release:perform" > > > > schedule it to somewhere in far future and run it ( one click) later > > > > > > never try it thou ;-) > > > > -D > > > > > > On 7/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > > > > I was wondering if anyone has developed any best practices for > performing > > > a release with maven when using continuum? To cut things down to the > basics, > > > seems you pretty much have to: > > > > > > 1. Stop continuum > > > 2. Perform the release (including deployment of jars to repository) > > > 3. Restart continuum > > > > > > Is this pretty much what everyone else is doing, or have other people > > > found better ways of managing releases in a continuous integration > > > environment. > > > > > > Thanks, > > > Baron > > > > > > > >
