title: How to automate version number update process for my Eclipse plugin built with Maven
body: <p>I working with a project similar to the project  <a href="http://www.vogella.com/articles/EclipseTycho/article.html" rel="noreferrer">described here</a>.
  So, it has a few modules in parent pom.xml:</p>
  
  
  
  <pre class="lang-xml prettyprint-override"><code> &lt;modules&gt;
      &lt;module&gt;../de.vogella.tycho.plugin&lt;/module&gt;
      &lt;module&gt;../de.vogella.tycho.feature&lt;/module&gt;
      &lt;module&gt;../de.vogella.tycho.p2updatesite&lt;/module&gt;
   &lt;/modules&gt;
  </code></pre>
  
  <p>These modules have a general version number e.g. <code>1.0.0-SNAPSHOT</code> or without <code>-SNAPSHOT</code>. The feature.xml file needs to contain the same version number:</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;feature
        id="com.my.feature"
        label="My plugin feature"
        version="1.0.0"&gt;
  </code></pre>
  
  <p>and:</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;plugin
        id="com.my.plugin"
        download-size="0"
        install-size="0"
        version="1.0.0"
        unpack="false"/&gt;
  </code></pre>
  
  <p>The files category.xml (in p2 update-site projects) and MANIFEST.MF (in plugin projects) need to contain the same value.</p>
  
  <p>The question is: How to automate the version number update process in all these files using Maven?</p>
  
  <p>I tried to resolve this problem using maven-release-plugin and maven-versions-plugin. The first plugin makes a lot of unused actions (like making a lot of CVS commits, which I do not use in this project). The second plugin only makes changes in pom.xml files and do not modify feature.xml, category.xml and MANIFEST.MF, or I used it not so good. </p>