[
https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297920#comment-297920
]
Mark Struberg commented on MRELEASE-719:
----------------------------------------
right, we have 2 options
a.) having release:prepare fail _early_ if the tag already exists. And have
release:rollback only WARN that the tag must get removed manually
b.) have release:rollback remove the tag as well if it exists _and_ we have
proper privileges. I'm always a bit reluctant fraidy-cat when doing a remove
operation on an SCM ...
I think having release:prepare fail _early_ if the tag already exists is a good
idea in any case.
> No error when release:prepare with an already existing scm tag
> --------------------------------------------------------------
>
> Key: MRELEASE-719
> URL: https://jira.codehaus.org/browse/MRELEASE-719
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.1
> Reporter: Tony Chemit
> Assignee: Olivier Lamy
> Fix For: 2.4
>
>
> When releasing the mojo-parent (codehaus), I had to do the release twice but
> I forgot to remove the scm tag.
> The release:prepare did not complain about it (should have).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
