Hi,

see MRELEASE-165 (release:prepare should fail if the tag already exists)[1]
The main reason why it is still not implemented, is that this must be solved in the SCM project. If we know how to do a valid(!) check of the existence of a tag for the scm providers, we could start implementing it. My experience is, is that these kind of issues only happen at the start of a new project. Once it works, it'll all stay fine.

About the rollback: it's already there: release:rollback[2]
And it works just as you described. However, if you do the release with the Jenkins m2-release-plugin, that plugin in still missing the rollback option[3].

thanks,
Robert

[1] https://jira.codehaus.org/browse/MRELEASE-165
[2] http://maven.apache.org/maven-release/maven-release-plugin/rollback-mojo.html
[3] https://issues.jenkins-ci.org/browse/JENKINS-8038

Op Fri, 31 Oct 2014 17:26:52 +0100 schreef Bernd Eckenfels <e...@zusammenkunft.net>:

Hello,

one thing which bites me quite regularly with the maven release plugin
is the fact, that it will update the POMs to the release version then
commit them and then tag them. If the tagging fails (especially because
the tag existed already) then it will leave the head on a released
version number.

This is in my case a problem as I have to go through a gerrit release
to change it to a snapshot version to try again.

A good improvement would be to first check the existence of the tag.
This would not cover all error cases but the most common.

Another option (or in addition to that), a rollback action would be to
actually commit the updated POM with the old snapshot version again?

(just to warn people, in my case if an integration build is triggert on
the master which has configured jenkins to deploy (normally the
snapshots) it will happyly deply the released version).

Gruss
Bernd

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to