Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<p>This page contains advice to ensure smooth transition to maven 3 from maven 2 :</p>

<h3>A set of maven-enforcer-plugin rule</h3>

<ul>
	<li>Check that plugin versions are defined</li>
	<li>TODO: Ensure that plugin defs appear only once</li>
	<li>TODO: More rules!</li>
</ul>

<table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>&lt;project>  [...]
  &lt;build>
    &lt;plugins>
      &lt;plugin>
        &lt;groupId>org.apache.maven.plugins&lt;/groupId>
        &lt;artifactId>maven-enforcer-plugin&lt;/artifactId>
        &lt;version>1.0&lt;/version>
        &lt;executions>
          &lt;execution>
            &lt;id>enforce-plugin-versions&lt;/id>
            &lt;goals>
              &lt;goal>enforce&lt;/goal>
            &lt;/goals>
            &lt;configuration>
              &lt;rules>
                &lt;requirePluginVersions>
                   &lt;message>Best Practice is to always define plugin versions!&lt;/message>
                   &lt;banLatest>true&lt;/banLatest>
                   &lt;banRelease>true&lt;/banRelease>
                   &lt;banSnapshots>true&lt;/banSnapshots>
                   &lt;phases>clean,deploy,site&lt;/phases>
                   &lt;additionalPlugins>
                     &lt;additionalPlugin>org.apache.maven.plugins:maven-eclipse-plugin&lt;/additionalPlugin>
                     &lt;additionalPlugin>org.apache.maven.plugins:maven-reactor-plugin&lt;/additionalPlugin>
                   &lt;/additionalPlugins>
                &lt;/requirePluginVersions>
                &lt;unCheckedPluginsList>org.apache.maven.plugins:maven-enforcer-plugin,org.apache.maven.plugins:maven-idea-plugin&lt;/unCheckedPluginsList>
              &lt;/rules>
            &lt;/configuration>
          &lt;/execution>
        &lt;/executions>
      &lt;/plugin>
    &lt;/plugins>
  &lt;/build>
  [...]
</pre></td></tr></table>
<p>&lt;/project&gt;</p>

<h3>relative path to parent</h3>
<p>If a project is referring to a parent pom, but that pom isn't reachable in the default parent path (../pom.xml). Then you should either :</p>
<ul>
	<li>update it to the right path</li>
	<li>put &lt;relativePath /&gt; in the &lt;parent&gt; tag so that maven knows it will have to look for it directly in the local repository</li>
</ul>

<h3>Standard variables</h3>
<p>For example, when one wants to refer to the artifactId of a POM, the variable ${project.artifactId} can be used. <br />
There are a lot of other possibilities to do that, like ${pom.artifactId}, ${artifactId} and so on. <br />
These ways are all deprecated and might be deleted in the future. With maven3, all these deprecated uses appear as warnings.</p>

<ul>
	<li>Always use the <strong>${project.xxx}</strong> form</li>
</ul>

<ol>
	<li>Thank JVZ for the page title: <a href="http://twitter.com/jvanzyl/status/4621533361">http://twitter.com/jvanzyl/status/4621533361</a></li>
</ol>