No, we don't have an extra version. The branch is called "int_module_1.0" and we use 1.0-SNAPSHOT on that branch. When we release, this becomes version 1.0 and no further work should be done on that branch. We will then create a new branch "int_module_1.1" and use version 1.1-SNAPSHOT there.
regards, Wim 2009/1/19 Mark Struberg <[email protected]> > but you haven an internal build version _inside_ this brunch, don't you? > > how should maven otherwise distinguish between different builds of that > branch? > > I suggest using: > int_module_1.0-1-SNAPSHOT > > so a release will create and tag a int_module_1.0-1 and your pom finally > will state int_module_1.0-2-SNAPSHOT > > LieGrue, > strub > > --- Wim Deblauwe <[email protected]> schrieb am Mo, 19.1.2009: > > > Von: Wim Deblauwe <[email protected]> > > Betreff: Perform release without updating pom to new SNAPSHOT version > > An: "Maven Users List" <[email protected]> > > Datum: Montag, 19. Januar 2009, 12:16 > > Hi, > > > > is it possible to do release:perfom which does everything > > like normal, > > except updating the pom.xml to a new SNAPSHOT version? > > > > We use branches per version, so if I release on my branch > > "int_module_1.0", > > I don't want the pom.xml to change to 1.1-SNAPSHOT. In > > fact, I want the > > branch to be locked. > > > > Is this supported by the release plugin? > > > > regards, > > > > Wim > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
