I also would be interested to hear how others are using the plugin... This is how we're using it:
New development happens on the trunk (and sometimes project branches), where the pom is 2.1.0-SNAPSHOT. At some point, we're happy (enough) with it that we create a release branch (e.g. 2.1.x), and run the plugin from there -- it creates the 2.1.0 tag, does the 2.1.0 deploy, and ups the version on the release branch to 2.1.1-SNAPSHOT. Future bug-fixes (if any) are made on the 2.1.x branch and when enough have accumulated, we run the plugin again, and now the pom is up to 2.1.2-SNAPSHOT. Then we merge the bug-fixes back down to the trunk. The one manual step in our process is updating the pom in the trunk to 2.2.0-SNAPSHOT after creating the branch. Is there a better way? Trevor Spackman -----Original Message----- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 12:13 PM To: Maven Users List Subject: Re: Releasing a branch? Hi Jim, I've been reading the replies you got, and I feel most of them didn't really understand your problem. I'm using the release-plugin as well, but I'll admit right away that I haven't tried it on branches yet. I believe it wasn't really thought for that though. At least, not automatically. Since I've been releasing internal versions here (0.x.x), I haven't had the need for branching, but I do think it is an issue that will come up as soon as we go 'live' here. It is something I've been wanting to test for some time now, but haven't gotten around to it. Maybe I'll get to it next week, seems I have a little spare time on my hands. So, unless someone really knows how to branch in maven and tells us all, I'm afraid you're stuck atm. I'll let you (and everybody else here) know what I find out when I come around to that testing... Sorry to be of no real help. On Thursday 26 April 2007 19:57, Crossley, Jim wrote: > 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 -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at --------------------------------------------------------------------- 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]
