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
