|
55 | 55 | <p>An XSD is available at:</p>
|
56 | 56 | <ul>
|
57 | 57 | <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>
|
58 |
| - <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> |
| 58 | + <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> |
59 | 59 | </ul>
|
60 | 60 | ]]>
|
61 | 61 | </description>
|
|
679 | 679 | <field>
|
680 | 680 | <name>defaultGoal</name>
|
681 | 681 | <version>3.0.0+</version>
|
682 |
| - <description>The default goal (or phase in Maven 2) to execute when none is specified for |
683 |
| - the project. Note that in case of a multi-module build, only the default goal of the top-level |
684 |
| - project is relevant, i.e. the default goals of child modules are ignored. Since Maven 3, |
685 |
| - multiple goals/phases can be separated by whitespace.</description> |
| 682 | + <description>The default goal to execute when none is specified for |
| 683 | + the project. In a multi-module build, only the default goal of the top-level |
| 684 | + project is relevant. That is, the default goals of child modules are ignored. |
| 685 | + Multiple goals can be separated by whitespace.</description> |
686 | 686 | <type>String</type>
|
687 | 687 | </field>
|
688 | 688 | <field>
|
|
1087 | 1087 | <version>3.0.0+</version>
|
1088 | 1088 | <description>
|
1089 | 1089 | <![CDATA[
|
1090 |
| - The version requirement of the dependency, e.g. <code>3.2.1</code>. The actual version will be resolved based on the usage context. |
1091 |
| - Version requirement can also be specified as a range of versions, e.g. <code>[3.2.0,)</code>. This is discouraged as it may break <i>predictability</i> of resolved version. |
1092 |
| - See <a href="https://s.apache.org/dependency-version">dependency version requirement documentation</a> |
1093 |
| - and <a href="https://s.apache.org/transitive-dependencies-resolution">transitive dependencies resolution</a> for more details. |
| 1090 | + The version requirement of the dependency such as <code>3.2.1</code>. |
| 1091 | + The actual version will be resolved by dependency mediation. |
| 1092 | + The version requirement can also be |
| 1093 | + specified as a range of versions such as <code>[3.2.0,)</code>. |
| 1094 | + However, this is discouraged since it may break <i>predictability</i> of |
| 1095 | + the resolved version. See the <a href="https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification">Dependency Version Requirement Specification</a> |
| 1096 | + and <a href="https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies">Transitive Dependencies</a> for more details. |
1094 | 1097 | ]]>
|
1095 | 1098 | </description>
|
1096 | 1099 | <type>String</type>
|
|
1401 | 1404 | <![CDATA[
|
1402 | 1405 | Gives the status of this artifact in the remote repository.
|
1403 | 1406 | This must not be set in your local project, as it is updated by
|
1404 |
| - tools placing it in the reposiory. Valid values are: <code>none</code> (default), |
1405 |
| - <code>converted</code> (repository manager converted this from an Maven 1 POM), |
| 1407 | + tools placing it in the repository. Valid values are: <code>none</code> (default), |
| 1408 | + <code>converted</code> (repository manager converted this from a Maven 1 POM), |
1406 | 1409 | <code>partner</code>
|
1407 |
| - (directly synced from a partner Maven 2 repository), <code>deployed</code> (was deployed from a Maven 2 |
| 1410 | + (directly synced from a partner Maven repository), <code>deployed</code> (was deployed from a Maven |
1408 | 1411 | instance), <code>verified</code> (has been hand verified as correct and final).
|
1409 | 1412 | ]]>
|
1410 | 1413 | </description>
|
|
2572 | 2575 | <description>
|
2573 | 2576 | <![CDATA[
|
2574 | 2577 | The priority of this execution compared to other executions which are bound to the same phase.
|
2575 |
| - <strong>Warning:</strong> This is an internal utility property that is only public for technical reasons, |
2576 |
| - it is not part of the public API. In particular, this property can be changed or deleted without prior |
| 2578 | + <strong>Warning:</strong> This is an internal utility property that is only public for technical reasons. |
| 2579 | + It is not part of the public API. In particular, this property can be changed or deleted without prior |
2577 | 2580 | notice.
|
2578 | 2581 | ]]>
|
2579 | 2582 | </description>
|
|
3142 | 3145 | <defaultValue>2.0</defaultValue>
|
3143 | 3146 | <description><![CDATA[
|
3144 | 3147 | For a plugin project (packaging is <code>maven-plugin</code>), the minimum version of
|
3145 |
| - Maven required to use the resulting plugin.<br> |
3146 |
| - In Maven 2, this was also specifying the minimum version of Maven required to build a |
3147 |
| - project, but this usage is <b>deprecated</b> in Maven 3 and not checked any more: use |
3148 |
| - the <a href="https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html">Maven Enforcer Plugin's |
3149 |
| - <code>requireMavenVersion</code> rule</a> instead. |
| 3148 | + Maven required to use the resulting plugin. |
3150 | 3149 | ]]>
|
3151 | 3150 | </description>
|
3152 | 3151 | <required>false</required>
|
|
0 commit comments