On Tue, Aug 19, 2008 at 11:42 PM, Alex Boisvert <[EMAIL PROTECTED]> wrote: > I agree with you, it's confusing. I would prefer to have: > > VERSION_NUMBER = '1.1.0-SNAPSHOT' > # No more NEXT_VERSION > > and do a release, the tag would be 1.1.0, released artifacts would be 1.1.0 > and after the release the new versions would be: > > VERSION_NUMBER = '1.1.1-SNAPSHOT' > > and if you want to change the next version number, edit the file and commit.
And what do you think of interactively asking the user the new version after tagging the release? Lacton > alex > > > On Tue, Aug 19, 2008 at 1:26 PM, lacton <[EMAIL PROTECTED]>wrote: > >> While trying to write some tests for the release task, I noticed a >> puzzling behavior. >> >> Let's say I have a buildfile with >> <code> >> VERSION_NUMBER = '1.1.0-SNAPSHOT' >> NEXT_VERSION = '1.2.0' >> </code> >> >> For me, this means I am currently developing the 1.1.0 version, and >> when I'm done, I will tag this as a 1.1.0 release and start working on >> the 1.2.0. >> >> Yet, when I call the release task, I get a tag called '1.2.0', not '1.1.0'. >> >> Am I off by one or is this a bug? >> >> Lacton
