[
https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297924#comment-297924
]
Mark Struberg commented on MRELEASE-719:
----------------------------------------
> Well, you don't 'remove' anything from a scm. You just create a new version..
That depends on the SCM. This statement is only true for SVN. CVS ditched it
sometimes even in it's attic (the first delete is fine, the 2nd destroyed the
attic). And in GIT if you push a removal of a tag, then it's gone... Of course
it's still in the downstream repos if they pulled it, but it's a history
rewrite which is often not allowed. It is perfectly fine though if
pushChanges=false for Hg and GIT! Needs a bit more brainwork I fear.
> 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
