<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Maven Release Plugin on ilikeorangutans</title><link>https://kuelzer.ca/tags/maven-release-plugin/</link><description>Recent content in Maven Release Plugin on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:27:24 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/maven-release-plugin/index.xml" rel="self" type="application/rss+xml"/><item><title>Maven Release Plugin and Git 1.9</title><link>https://kuelzer.ca/posts/2014/04/29/maven-release-plugin-and-git-19/</link><pubDate>Tue, 29 Apr 2014 13:59:40 -0400</pubDate><guid>https://kuelzer.ca/posts/2014/04/29/maven-release-plugin-and-git-19/</guid><description>&lt;p&gt;Ran into this issue today and wasted a good hour on figuring out what happened. Seems to be an issue with Git 1.9.x.&lt;/p&gt;
&lt;h3 id="symptoms"&gt;Symptoms&lt;/h3&gt;
&lt;p&gt;Maven release plugin successfully completes the &lt;code&gt;release:prepare&lt;/code&gt; goal, creates the tag, but fails to commit the changed &lt;code&gt;pom.xml&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="solution"&gt;Solution&lt;/h3&gt;
&lt;p&gt;Git&amp;rsquo;s output format changed slightly in one of the recent versions and Maven&amp;rsquo;s SCM provider expects output in a certain way. Luckily you can force git to use the old output style:&lt;/p&gt;</description></item></channel></rss>