This is an automated email from the ASF dual-hosted git repository. elharo pushed a commit to branch mdo3 in repository https://gitbox.apache.org/repos/asf/maven.git
commit b7e546866aef03a4ea6af829c974a9274b84d8b8 Author: Elliotte Rusty Harold <elh...@ibiblio.org> AuthorDate: Thu Jun 5 09:21:25 2025 -0400 [MNGSITE-393] remove references to Maven 2 --- maven-model/src/main/mdo/maven.mdo | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/maven-model/src/main/mdo/maven.mdo b/maven-model/src/main/mdo/maven.mdo index 6e33f192fd..af1c943d57 100644 --- a/maven-model/src/main/mdo/maven.mdo +++ b/maven-model/src/main/mdo/maven.mdo @@ -55,7 +55,7 @@ <p>An XSD is available at:</p> <ul> <li><a href="https://maven.apache.org/xsd/maven-v3_0_0.xsd">https://maven.apache.org/xsd/maven-v3_0_0.xsd</a> for Maven 1.1.</li> - <li><a href="https://maven.apache.org/xsd/maven-4.0.0.xsd">https://maven.apache.org/xsd/maven-4.0.0.xsd</a> for Maven 2.0.</li> + <li><a href="https://maven.apache.org/xsd/maven-4.0.0.xsd">https://maven.apache.org/xsd/maven-4.0.0.xsd</a> for Maven 3.0.</li> </ul> ]]> </description> @@ -679,10 +679,10 @@ <field> <name>defaultGoal</name> <version>3.0.0+</version> - <description>The default goal (or phase in Maven 2) to execute when none is specified for - the project. Note that in case of a multi-module build, only the default goal of the top-level - project is relevant, i.e. the default goals of child modules are ignored. Since Maven 3, - multiple goals/phases can be separated by whitespace.</description> + <description>The default goal to execute when none is specified for + the project. In a multi-module build, only the default goal of the top-level + project is relevant. That is, the default goals of child modules are ignored. + Multiple goals/phases can be separated by whitespace.</description> <type>String</type> </field> <field> @@ -1087,7 +1087,7 @@ <version>3.0.0+</version> <description> <![CDATA[ - The version of the dependency, e.g. <code>3.2.1</code>. In Maven 2, this can also be + The version of the dependency such as <code>3.2.1</code>. This can also be specified as a range of versions. ]]> </description> @@ -1399,10 +1399,10 @@ <![CDATA[ Gives the status of this artifact in the remote repository. This must not be set in your local project, as it is updated by - tools placing it in the reposiory. Valid values are: <code>none</code> (default), - <code>converted</code> (repository manager converted this from an Maven 1 POM), + tools placing it in the repository. Valid values are: <code>none</code> (default), + <code>converted</code> (repository manager converted this from a Maven 1 POM), <code>partner</code> - (directly synced from a partner Maven 2 repository), <code>deployed</code> (was deployed from a Maven 2 + (directly synced from a partner Maven repository), <code>deployed</code> (was deployed from a Maven instance), <code>verified</code> (has been hand verified as correct and final). ]]> </description> @@ -3140,11 +3140,7 @@ <defaultValue>2.0</defaultValue> <description><![CDATA[ For a plugin project (packaging is <code>maven-plugin</code>), the minimum version of - Maven required to use the resulting plugin.<br> - In Maven 2, this was also specifying the minimum version of Maven required to build a - project, but this usage is <b>deprecated</b> in Maven 3 and not checked any more: use - the <a href="https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html">Maven Enforcer Plugin's - <code>requireMavenVersion</code> rule</a> instead. + Maven required to use the resulting plugin. ]]> </description> <required>false</required>