[ https://jira.codehaus.org/browse/MRELEASE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358064#comment-358064 ]
Martin Todorov commented on MRELEASE-572: ----------------------------------------- I don't think this task should be closed. @Jens Beyer: Could you check if the issue can still be reproduced? If it still re-occurs, let's re-open this task. > release:prepare does not check for existing tag and updates the tag in a > wrong way > ---------------------------------------------------------------------------------- > > Key: MRELEASE-572 > URL: https://jira.codehaus.org/browse/MRELEASE-572 > Project: Maven Release Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-9 > Reporter: Jens Beyer > > If the targetted release tag already exists (like accidentally re-releasing a > version), release:prepare does not complain about already existing tag, and > updates the tag in a wrong way. > Example: I call mvn release:prepare on my-project-1.0.0-SNAPSHOT. The tag > my-project-1.0.0 already exists. > Expected result: mvn fails with the error "version tag my-project-1.0.0 > already exists in SCM" > Current result: my-project-1.0.0 tag (!) is updated, with a new subdirectory > called 'my-project', below that is the expected result of the re-release; the > old data of the tag is still present. > I'd rather never update a tag (hence I'd like it to fail). That's why I > tagged it. -- This message was sent by Atlassian JIRA (v6.1.6#6162)