Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This page contains advice to ensure smooth transition to maven 3 from maven 2 :

A set of maven-enforcer-plugin rule

  • Check that plugin versions are defined
  • TODO: Ensure that plugin defs appear only once
  • TODO: More rules!

</project>

relative path to parent

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 :

  • update it to the right path
  • put <relativePath /> in the <parent> tag so that maven knows it will have to look for it directly in the local repository

Standard variables

When one wants to refer to the artifactId of a POM, the variable $

Unknown macro: {project.artifactId}

can be used.
There are a lot of other possibilities to do that, like $

Unknown macro: {pom.artifactId}

, $

Unknown macro: {artifactId}

and so on.
These ways are all deprecated and might be deleted in the future. With maven3, all these deprecated uses appear as warnings.

  • Always use *$
    Unknown macro: {project.xxx}
    * and no more $
    Unknown macro: {pom.xxx}
    or $
    Unknown macro: {xxx}
  1. Thank JVZ for the page title: http://twitter.com/jvanzyl/status/4621533361
  • No labels