You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jens Beyer (JIRA)" <ji...@codehaus.org> on 2010/06/09 11:31:12 UTC

[jira] Created: (MRELEASE-572) release:prepare does not check for existing tag and updates the tag in a wrong way

release:prepare does not check for existing tag and updates the tag in a wrong way
----------------------------------------------------------------------------------

                 Key: MRELEASE-572
                 URL: http://jira.codehaus.org/browse/MRELEASE-572
             Project: Maven 2.x 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRELEASE-572) release:prepare does not check for existing tag and updates the tag in a wrong way

Posted by "Martin Todorov (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269990#action_269990 ] 

Martin Todorov commented on MRELEASE-572:
-----------------------------------------

This is a more than sane check, which I believe needs to be implemented.

> release:prepare does not check for existing tag and updates the tag in a wrong way
> ----------------------------------------------------------------------------------
>
>                 Key: MRELEASE-572
>                 URL: http://jira.codehaus.org/browse/MRELEASE-572
>             Project: Maven 2.x 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira