Thanks all for the quick replies. So it seems my mistake was not cutting the original release from the branch, i.e. I should've created the branch before I cut the release. This sounds sensible, except for two things:
1) I'd rather not create a branch for every release; I'd rather create the branch from the release tag only when a reported bug forces me to. -- but more importantly -- 2) Creating the branch means I'll have to cut the same release twice, once in each branch. If my target is 2.0.2.1-SNAPSHOT in the HEAD, and I want to release 2.0.2.1 and begin adding features for 2.0.3 (the third number indicates feature differences in our company convention) in the HEAD. If I branch HEAD to 2.0.2, I then must release 2.0.2.1 in the 2.0.2 branch and update the target version of HEAD to 2.0.3.1-SNAPSHOT. That would require me to run the release plugin in both branches. That seems a little goofy, no? I suppose I could keep the version of HEAD at 2.0-SNAPSHOT and *never* release from HEAD. I would only release from a branch with an additional digit, e.g. 2.0.2. When that branch is initially created, the pom's version would be 2.0-SNAPSHOT, but I could override the defaults of release:prepare to set the version at 2.0.2.1 with the next version being 2.0.2.2-SNAPSHOT. Do you think that's the easiest way? I'd be interested in hearing how other Maven users deal with the "multiple versions in production requiring fixes without new features" problem. Thanks, Jim -----Original Message----- From: Trevor Spackman [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 1:12 PM To: Maven Users List Subject: RE: Releasing a branch? I'm using the release plugin on a very regular basis, and it makes things very smooth. When you release 1.0.1-SNAPSHOT, the plugin creates a artifactId-1.0.1 tag in the SCM (and updates the scm in the tag's pom). Then it checks the code out off that tag and runs a deploy against the newly-checked-out code. The release version is on a tag. So, when you used the plugin against 2.0.2.1-SNAPSHOT, it should have been on the 2.0.2 branch already. Then when the plugin updated the 2.0.2 branch's pom (with the value you specified in response to the "What is the new development version for "Project Name"?) it should have been automatically defaulted to 2.0.2.2-SNAPSHOT. You're ready to release again without any pom changes. Trevor Spackman -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 10:55 AM To: Maven Users List Subject: Re: Releasing a branch? How did you "use the release plugin"? Unless I'm mistaken, proper use of the plugin will result in a release being generated with fixed version number, commit to SCM, then poms updated back to SNAPSHOT and committed to SCM again. I'm not currently using the release plugin myself so I'm not positive. But I'm about to start using it, and this is what I expect based on my reading of documentation and emails on this list thus far. Wayne On 4/26/07, Crossley, Jim <[EMAIL PROTECTED]> wrote: > I used the release plugin to successfully release version 2.0.2.1 of our > project. We continued working on the HEAD targeting version 2.0.3 while > QA tested 2.0.2.1. To address bugs reported against that release, we > created a 2.0.2 branch in CVS. We applied our fixes there. > > Now it's time to create version 2.0.2.2 from that 2.0.2 branch. When I > attempt to run release:prepare, it immediately fails because the version > is not a SNAPSHOT. Of course it's not a snapshot. It's a released > version requiring bug fixes. > > What did I do wrong? Is the maven release model such that releases are > only ever cut from the HEAD? How do you account for > "bugfixes-without-new-features" then? > > Do I need to manually update the versions of all the subprojects myself > and then manually tag it? It seems kinda silly to change all the > versions to 2.0.2.1-SNAPSHOT just so I can have the release plugin > change them to 2.0.2.2! I may as well do that myself and eliminate the > middle man, right? > > Having the release plugin automatically update all the versions of my > multi-module project is a beautiful thing. It seems kind of arbitrary > to me that the feature only works when the existing version contains the > suffix, "-SNAPSHOT", doesn't it? > > Thanks, > Jim > > --------------------------------------------------------------------- > 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]
