Author: hboutemy Date: Sun Sep 18 22:27:12 2016 New Revision: 1761368 URL: http://svn.apache.org/viewvc?rev=1761368&view=rev Log: [MNG-5297] update the into on prerequisites to show the change in Maven 3
Modified: maven/site/trunk/content/apt/pom.apt Modified: maven/site/trunk/content/apt/pom.apt URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/pom.apt?rev=1761368&r1=1761367&r2=1761368&view=diff ============================================================================== --- maven/site/trunk/content/apt/pom.apt (original) +++ maven/site/trunk/content/apt/pom.apt Sun Sep 18 22:27:12 2016 @@ -1588,11 +1588,17 @@ scm:cvs:pserver:127.0.0.1:/cvs/root:my-p * {Prerequisites} - The POM may have certain prerequisites in order to execute correctly. For example, + The POM may have certain prerequisites in order to execute correctly. For example, perhaps there was a fix in Maven 2.0.3 that you need in order to deploy using sftp. - Here is where you give the prerequisites to building. If these are not met, Maven will + + In Maven 3, use + {{{/enforcer/enforcer-rules/requireMavenVersion.html} Maven Enforcer Plugin's <<<requireMavenVersion>>> rule}}, + or other rules to check other aspects. + + In Maven 2, here is where you give the prerequisites to building: if these are not met, Maven will fail the build before even starting. The only element that exists as a prerequisite in - POM 4.0 is the maven element, which takes a minimum version number. + POM 4.0 is the <<<maven>>> element, which takes a minimum version number. It is checked with Maven 2, it is not any + more in Maven 3. +-------------------------+ <project xmlns="http://maven.apache.org/POM/4.0.0" @@ -1915,7 +1921,7 @@ scm:cvs:pserver:127.0.0.1:/cvs/root:my-p * <<jdk>>: <<<activation>>> has a built in, Java-centric check in the <<<jdk>>> element. This will activate if the test is run under a jdk version number that matches the prefix given. In the above example, <<<1.5.0_06>>> - will match. Ranges are also supported as of Maven 2.1. See the {{{https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html} maven-enforcer-plugin}} for more details about supported ranges. + will match. Ranges are also supported as of Maven 2.1. See the {{{/enforcer/enforcer-rules/versionRanges.html} maven-enforcer-plugin}} for more details about supported ranges. * <<os>>: The <<<os>>> element can define some operating system specific properties shown above. See the maven-enforcer-plugins {{{https://maven.apache.org/enforcer/enforcer-rules/requireOS.html}RequireOS Rule}} for more details about OS values.