On Tue, May 12, 2009 at 8:57 PM, James Carman <ja...@carmanconsulting.com> wrote: > We could probably use the release plugin to create a branch for each > rc, right? Then, run the release process off that branch and it'll > create the correct tag.
How can one configure this? I think it can be done somehow in th eparent pom but.... I'll try the way Dan suggested > > On Tue, May 12, 2009 at 1:41 PM, Dan Fabulich <d...@fabulich.com> wrote: >> When I ran it, the release plugin prompted me for the tag name to create. >> Rather than accept defaults, I manually typed in the appropriate tag name. >> >> -Dan >> >> Christian Grobmeier wrote: >> >>> Hi, >>> currently the >>> mvn -Prc release:perform >>> >>> creates a tag with the release name instead of f.e. >>> commons-compress-1_0-RC1. >>> >>> 1) Do I have to remove the tag commons-compress-1_0 manually when >>> doing a second release candidate? Just want to make sure, don't want >>> to break the rules. >>> >>> 2) Is it really good to have a tag named like this instead with a >>> suffix RC1 or whatever? >>> >>> And yes, I will update: >>> http://wiki.apache.org/commons/CreatingReleases >>> with your answers :-) >>> >>> Best, >>> Christian >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
