Using Maven scm:checkin to commit changes to module projects
<p>I have a multi-module POM file:</p>

<pre><code>...
&lt;modules&gt;
   &lt;module&gt;../project1&lt;/module&gt;
   &lt;module&gt;../project2&lt;/module&gt;
   &lt;module&gt;../project3&lt;/module&gt;
   ...
&lt;/modules&gt;
...
</code></pre>

<p>Each of the modules is itself a Maven project with its own POM. Inside each of these POMs I have the <code>scm</code> tag defined with the <code>developerConnection</code> specified like this: </p>

<pre><code>&lt;scm&gt;
   &lt;developerConnection&gt;scm:svn:svn://hostname:port/path/to/trunk&lt;/developerConnection&gt;
&lt;/scm&gt;
</code></pre>

<p>My goal is to run the following Maven goals/options:</p>

<pre><code>versions:update-parent versions:commit scm:checkin \
  -Dmessage="automated commit" -Dusername=user -Dpassword=pass
</code></pre>

<p><strong>My expected results are:</strong></p>

<ol>
<li>The parent of each module's POM is updated to the latest released version.</li>
<li>The changes to each POM would be checked in to the SVN path specified in the POM for the module. E.g. <code>project1</code> POM checked in using <code>project1</code> <code>&lt;scm&gt;/&lt;developerConnection&gt;</code> path, <code>project2</code> checked in using <code>project2</code> path, etc.</li>
</ol>

<p><strong>Actual Results:</strong></p>

<ol>
<li>The parent of each module's POM is updated to latest released version. <strong>This works as expected.</strong></li>
<li><strong>Only</strong> the multi-module POM is checked in to SVN, <strong>none</strong> of the module POMs are checked in. <strong>This is the problem.</strong></li>
</ol>

<p>Is there a way to achieve the expected results above or is this something that the SCM plugin simply was not designed to do? If it is possible, how would I modify what I have in order to get the results I want?</p>

<p><strong>Note</strong>: I can't change the project structure - I can't put the modules inside of the parent project, they have to remain separate. </p>

<p>Not sure if it's relevant but I'm using Maven 3.3.9.</p>