You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wim Deblauwe (JIRA)" <ji...@codehaus.org> on 2013/06/13 10:10:03 UTC
[jira] (MRELEASE-842) Allow not updating the pom after tagging
during release:prepare
Wim Deblauwe created MRELEASE-842:
-------------------------------------
Summary: Allow not updating the pom after tagging during release:prepare
Key: MRELEASE-842
URL: https://jira.codehaus.org/browse/MRELEASE-842
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Affects Versions: 2.3.2
Reporter: Wim Deblauwe
I am using the release plugin with Maven and git. I also follow the gitflow convention and am using what is described here (http://vincent.demeester.fr/2012/07/maven-release-gitflow/) to do my releases.
I would like to be able to specify that the prepare goal should do everything it does now, but *not* update the pom.xml again after the tagging to a new SNAPSHOT version. It should also not ask for it ofcourse at the start of the release:prepare.
Now I have to invent a version which is never going to be used anyway and I would like to avoid the extra commit on the release branch. It would also avoid having to do the trick with the merge from HEAD-1 which can be easily forgotten.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira