[
https://issues.apache.org/jira/browse/MRELEASE-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-842.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Allow not updating the pom after tagging during release:prepare
> ---------------------------------------------------------------
>
> Key: MRELEASE-842
> URL: https://issues.apache.org/jira/browse/MRELEASE-842
> Project: Maven Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.2
> Reporter: Wim Deblauwe
> Priority: Major
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
