svn commit: r1838391 - in /maven/website/content: guides/introduction/introduction-to-the-pom.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Sun Aug 19 16:49:34 2018
New Revision: 1838391

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/introduction/introduction-to-the-pom.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/guides/introduction/introduction-to-the-pom.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-pom.html (original)
+++ maven/website/content/guides/introduction/introduction-to-the-pom.html Sun Aug 19 16:49:34 2018
@@ -557,7 +557,7 @@ Brett Porter" />
 <div class="section">
 <h5><a name="The_Scenario"></a>The Scenario</h5>
 <p>However, that would work if the parent project was already installed in our local repository or was in that specific directory structure (parent <tt>pom.xml</tt> is one directory higher than that of the module's <tt>pom.xml</tt>).</p>
-<p>But what if the parent is not yet installed and if the directory structure is</p>
+<p>But what if the parent is not yet installed and if the directory structure is as in the following example?</p>
 <div class="source"><pre class="prettyprint linenums">.
  |-- my-module
  |   `-- pom.xml
@@ -581,14 +581,14 @@ Brett Porter" />
 <h3><a name="Project_Aggregation">Project Aggregation</a></h3>
 <p>Project Aggregation is similar to <a href="#Project_Inheritance">Project Inheritance</a>. But instead of specifying the parent POM from the module, it specifies the modules from the parent POM. By doing so, the parent project now knows its modules, and if a Maven command is invoked against the parent project, that Maven command will then be executed to the parent's modules as well. To do Project Aggregation, you must do the following:</p>
 <ul>
-<li>Change the parent POMs packaging to the value &quot;pom&quot; .</li>
-<li>Specify in the parent POM the directories of its modules (children POMs)</li></ul>
+<li>Change the parent POMs packaging to the value &quot;pom&quot;.</li>
+<li>Specify in the parent POM the directories of its modules (children POMs).</li></ul>
 <p><a href="./introduction-to-the-pom.html">[top]</a></p>
 <div class="section">
 <h4><a name="Example_3">Example 3</a></h4>
 <div class="section">
 <h5><a name="The_Scenario"></a>The Scenario</h5>
-<p>Given the previous original artifact POMs, and directory structure,</p>
+<p>Given the previous original artifact POMs and directory structure:</p>
 <p><b>com.mycompany.app:my-app:1's POM</b></p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
@@ -635,7 +635,7 @@ Brett Porter" />
  |   `-- pom.xml
  `-- parent
      `-- pom.xml</pre></div>
-<p>How would the parent pom specify its modules?</p></div>
+<p>How would the parent POM specify its modules?</p></div>
 <div class="section">
 <h5><a name="The_Solution"></a>The Solution</h5>
 <p>The answer? - the same way as Example 3, by specifying the path to the module.</p>

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