Maven release plugin - resolving RELEASE version of parent when tagging
<p>I release projects using maven release plugin. Version of parent-pom is set to 'RELEASE'. </p>

<p>Like this: </p>

<pre><code>&lt;parent&gt;
    &lt;groupId&gt;my.group.id&lt;/groupId&gt;
    &lt;artifactId&gt;my-parent-pom&lt;/artifactId&gt;
    &lt;version&gt;RELEASE&lt;/version&gt;
&lt;/parent&gt;
&lt;artifactId&gt;My Application&lt;/artifactId&gt;
&lt;version&gt;1.1.1-SNAPSHOT&lt;/version&gt;
</code></pre>

<p>Are there any ways to get the release-plugin to tag project in git with actual parent-pom version, while still keeping RELEASE in master/branch?</p>

<p>I would like pom.xml in tag (only) to look like this: </p>

<pre><code>&lt;parent&gt;
    &lt;groupId&gt;my.group.id&lt;/groupId&gt;
    &lt;artifactId&gt;my-parent-pom&lt;/artifactId&gt;
    &lt;version&gt;2.4.2&lt;/version&gt;
&lt;/parent&gt;
&lt;artifactId&gt;My Application&lt;/artifactId&gt;
&lt;version&gt;1.1.1&lt;/version&gt;
</code></pre>

<p>In most cases I need to use latest RELEASE of parent. E.g. To make sure CI server build and test all children upon new parent release. However, if i later need to go back to a previous tag I will have to manually figure out which version of the parent pom was used at the time it was first tagged. </p>

<p>The only way I can think of doing this is to use 'versions plugin' to resolve parent before releasing, then make sure to revert to 'RELEASE' afterwards. To me this sounds like a messy option as developers are going to forget it all the time, not to mention the extra hassle and git-pushing with each and every release. </p>