Dan, why does the build label require releasing? We have anthill label our daily build source but that doesn't require releasing... Can't you just use the scm:tag goal at the end of your build?
-----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Friday, April 21, 2006 9:33 AM To: Maven Developers List Subject: Re: release:auto-release Mike, at my work, each daily build must accompany a label. So cut the daily release is the way to go. I also work with another smaller project that adopting maven release process where daily build is from the snapshot build, we only cut a release when a millestone reaches. -D On 4/21/06, Mike Perham <[EMAIL PROTECTED]> wrote: > > Why would you ever want to auto-release something? Isn't a release > done when the module owner believes it is stable, not on an scheduled > time table? I would think a daily release should take the form of a > SNAPSHOT. > > -----Original Message----- > From: dan tran [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 20, 2006 11:39 PM > To: Maven Developers List > Subject: release:auto-release > > Hello all, > > At my work place, we have a requirement to do daily release using > maven-release-plugin. > So I create a custom plugin to run both release:prepare and > release:perform in one shot. > > If there are enought interests, I can merge it into > maven-release-plugin in a new mojo > > The mojo auto assign a tag with ${prefix}-${version}. prerfix has a > default value ${artifactId} of the root pom > > > WDYT? > > -Dan > > > --------------------------------------------------------------------- > 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]
