why not use mvn scm:branch to move to a branch and then make the release from the branch and finally remove the branch
On Thu, Jul 17, 2008 at 1:46 PM, Stephen Duncan Jr <[EMAIL PROTECTED]> wrote: > I want to use the release plugin to make testing releases, without > interrupting ongoing development. So, for example I want to take a project > that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT. I > want to make a release for 1.0-beta-1, with the dependencies at 1.0-beta-1 > (assume I've already made those releases). And then I want trunk to be back > at 1.0-SNAPSHOT for the version and dependencies. > > Right now, that almost works, except the release plugin won't accept > 1.0-SNAPSHOT as the "new development version" for the dependencies. Should > I enter that as a feature request/bug? Is there a better practice I should > follow? > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
