svn commit: r1884830 - in /maven/website/content: maven-site-1.0-site.jar pom.html

[sv...@apache.org]

Author: svn-site-role
Date: Sat Dec 26 22:24:18 2020
New Revision: 1884830

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/maven-site-1.0-site.jar
    maven/website/content/pom.html

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.

Modified: maven/website/content/pom.html
==============================================================================
--- maven/website/content/pom.html (original)
+++ maven/website/content/pom.html Sat Dec 26 22:24:18 2020
@@ -655,7 +655,7 @@ Display parameters as parsed by Maven (i
 <h5><a name="A_final_note_on_Inheritance_v._Aggregation"></a>A final note on <a name="Inheritance_v._Aggregation">Inheritance v. Aggregation</a></h5>
 <p>Inheritance and aggregation create a nice dynamic to control builds through a single, high-level POM. You often see projects that are both parents and aggregators. For example, the entire Maven core runs through a single base POM <a class="externalLink" href="https://svn.apache.org/viewvc/maven/maven-3/trunk/pom.xml?view=markup"><code>org.apache.maven:maven</code></a>, so building the Maven project can be executed by a single command: <code>mvn compile</code>. However, an aggregator project and a parent project are both POM projects, they are not one and the same and should not be confused. A POM project may be inherited from - but does not necessarily have - any modules that it aggregates. Conversely, a POM project may aggregate projects that do not inherit from it.</p></section></section></section><section>
 <h3><a name="Properties">Properties</a></h3>
-<p>Properties are the last required piece to understand POM basics. Maven properties are value placeholder, like properties in Ant. Their values are accessible anywhere within a POM by using the notation <code>${X}</code>, where <code>X</code> is the property. Or they can be used by plugins as default values, for example:</p>
+<p>Properties are the last required piece to understand POM basics. Maven properties are value placeholders, like properties in Ant. Their values are accessible anywhere within a POM by using the notation <code>${X}</code>, where <code>X</code> is the property. Or they can be used by plugins as default values, for example:</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;properties&gt;