I've read that, but I must be missing something. The incrementing happens if you use the deploy for a snapshot.
If you use the release plugin, you tell it the version to release. -----Original Message----- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 4:42 PM To: Maven Users List Subject: Re: Releasing Software Read Better Builds with Maven. It has a section on version numbering. If you follow that standard Maven should be able to increment the numbers for you. And as someone rightly pointed out, you never re-release the same version. Any changes made implies a new version, which would increment the RC number. On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote: > When I referred to SNAPSHOT, I was talking about the actual module that you > are building.. > > Say you have: > > 1.0-SNAPSHOT > > And you go to release > > Then release plugin prompts 1.0 > You change to 1.0RC1 > Then release plugin promts 1.1-SNAPSHOT for the next version.. > > However could you do this.. > > 1.0RC1-SNASHOT > > Then release plugin prompts 1.0RC1? > But then I'm not sure if it will increment properly... > > d- > > -----Original Message----- > From: Riegel, Holger [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 29, 2006 9:36 AM > To: Maven Users List > Subject: RE: Releasing Software > > This is how I do it: > > 1. Create a release branch in your version control system (e.g. > Subversion or CVS). > 2. Checkout the branch and use release:prepare and release:perform. The > tag name is some kind of x.yRCn, where n is the number of the relese > candidate. Just do bug fixing on the release branch, implement new > features on the trunk only. > 3. Let QA do its work. Fix the reported bugs, release a new release > candidate. > 4. If there are no more bugs found, rerelease the last release candidate > with the version number x.y. > > My advice: don' use snapshots for releases. The release plugin warns > you, if there are still snapshot dependencies in your poms. The reason > is that builds that use poms with snapshots cannot be reproduced: they > may yield another result when rebuilt later. > > Cheers, Holger > > -----Original Message----- > From: Douglas Ferguson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 29, 2006 4:15 PM > To: users > Subject: Releasing Software > > > I have been playing with the release plugin and it is really cool. > > > > However, I am curious about how folks are applying process on top of the > tool. > > > > If you are developing a snapshot and you are ready to release the new > version, then you run the release plugin. > > What happens when qa finds a defect and now you have to re-release the > same version? > > > > Here are some thoughts: > > > > 1) QA could test snap shot builds, but how do you perform a > release since snapshot aren't tagged and it could be difficult to know > you are releasing the same thing as a snapshot > > 2) Perhaps use a qualifier i.e. RC in the version when you > release? This way you can manually increment as you build. Can > qualifiers still be present with -SNAPSHOT? Or is snapshot a specially > qualifier? > > 3) Just release the software and if it needs to be re-released, > then release it again or release it with a new build number? > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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]
