> Todd Thiessen wrote: >> The first modification of the pom changes the version to remove the >> "-SNAPSHOT" and also changes the SCM values to point to the tag location >> instead of the trunk location. Once done, it then commits this change >> to trunk.
To some extent I think there's a reason for this, which is so that the files will not appear to have been modified on the tag, and the tag is a straight copy of some actual SVN revision, rather than being created out of thin air from a working copy. (Of course, if you branch from a tag and have it increment the branch version numbers, it straight-up modifies the tag and then modifies it back, which bugs me.) Something similar is done when branching - version numbers are updated beforehand, then branched, so that the set of revisions on the branch doesn't include the version number change. I guess this is so when you merge over all changes on the branch to the turnk, you don't get a bunch of spurious version number changes that you'd have to ignore. >> Can anyone else confirm this? This seems pretty dangerous. Certainly confirmable. I guess the main danger is really if someone updates and does a 'mvn deploy' and it blows away your release version. Keeping your release deployment credentials close is good practice, so this would be pretty uncommon in the wild. But it's an issue that maybe bears rethinking nonetheless. - John Stoneham --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
