[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MRELEASE-719: -- Fix Version/s: (was: 2.5) Backlog No error when release:prepare with an already existing scm tag -- Key: MRELEASE-719 URL: https://jira.codehaus.org/browse/MRELEASE-719 Project: Maven Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.2.1 Reporter: Tony Chemit Assignee: Olivier Lamy Fix For: Backlog 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298042#comment-298042 ] Emmanuel Lécharny commented on MRELEASE-719: You're right. I had SVN in mind. It's a bit sad that some SCM consider that removing a tag == deleting it totally, but you'll have to deal with such a stupid decision. Hopefully, you have a clue about the used SCM, so the plugin can behave accordingly. Note that it will requires way more work :) 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298046#comment-298046 ] Mark Struberg commented on MRELEASE-719: I'm not worried about the additional work needed. But I'm really worried that we pack all this information in our maven-release-manager. There is already way too much hardcoded stuff which is specific for single SCMs in there. I'd rather move all this information into the scm-api instead. 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297919#comment-297919 ] Emmanuel Lécharny commented on MRELEASE-719: The mvn release:rollback should at least remove the tag... 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297922#comment-297922 ] Emmanuel Lécharny commented on MRELEASE-719: Well, you don't 'remove' anything from a scm. You just create a new version... So removing the tag when doing a release:rollback is a no brainer, IMO. And, yes, a warning when doing a release:prepare if the tag already exists would definitively help ! 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-719: Fix Version/s: (was: 2.3) 2.4 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=293764#comment-293764 ] Dan Tran commented on MRELEASE-719: --- I ran into the same issue where I forgot the remove the bad svn tag, release:perpare went thru without error, and therefor release:perform picks up the wrong source 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.3 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291189#comment-291189 ] Tom Vaughan commented on MRELEASE-719: -- I'm confused about this ticket...does this bug report situation A or B? A) there already exists a tag directory out on the remote svn_root of the name that I enter during the mvn release:prepare phase or B) there already exists an scmdeveloperConnectionsvn:///blah/blah/tags/developerConnection/scm xml element in the pom of an artifact I'm about to release 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.3 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290268#comment-290268 ] Robert Scholte commented on MRELEASE-719: - This might be a svn server-side issue. I can confirm that this can go wrong at codehaus, but I've installed a complete system on a laptop and here the release stops if the tag already exists. 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.3 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
[jira] (MRELEASE-719) No error when release:prepare with an already existing scm tag
[ https://jira.codehaus.org/browse/MRELEASE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-719: -- Fix Version/s: 2.3 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 Fix For: 2.3 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
