svn commit: r857954 - in /websites/staging/maven/trunk/content: ./ guides/introduction/introduction-to-the-pom.html maven-site-1.0-site.jar

[buildbot]

Author: buildbot
Date: Wed Apr 10 08:14:59 2013
New Revision: 857954

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-pom.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 10 08:14:59 2013
@@ -1 +1 @@
-1466370
+1466372

Modified: 
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-pom.html
==============================================================================
--- 
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-pom.html
 (original)
+++ 
websites/staging/maven/trunk/content/guides/introduction/introduction-to-the-pom.html
 Wed Apr 10 08:14:59 2013
@@ -599,7 +599,7 @@ Brett Porter" />
   <modules>
     <module>my-module</module>
   </modules>
-&lt;/project&gt;</pre></div><p>In the revised com.mycompany.app:my-app:1, the 
packaging section and the modules sections were added. For the packaging, it's 
value was set to &quot;pom&quot;, and for the modules section, we have the 
element <tt>&lt;module&gt;my-module&lt;/module&gt;</tt>. The value of 
<tt>&lt;module&gt;</tt> is the relative path from the 
com.mycompany.app:my-app:1 to com.mycompany.app:my-module:1's POM (<i>by 
practice, we use the module's artifactId as the module directory's 
name</i>).</p><p>Now, whenever a Maven command processes 
com.mycompany.app:my-app:1, that same Maven command would be ran against 
com.mycompany.app:my-module:1 as well. Furthermore, some commands (goals 
specifically) handle project aggregation differently.</p><p><a 
href="./introduction-to-the-pom.html">[top]</a></p></div></div><div 
class="section"><h4><a name="Example_4">Example 4</a></h4><div 
class="section"><h5>The Scenario<a name="The_Scenario"></a></h5><p>But what if 
we change the dir
 ectory structure to the following:</p><div class="source"><pre>.
+&lt;/project&gt;</pre></div><p>In the revised com.mycompany.app:my-app:1, the 
packaging section and the modules sections were added. For the packaging, its 
value was set to &quot;pom&quot;, and for the modules section, we have the 
element <tt>&lt;module&gt;my-module&lt;/module&gt;</tt>. The value of 
<tt>&lt;module&gt;</tt> is the relative path from the 
com.mycompany.app:my-app:1 to com.mycompany.app:my-module:1's POM (<i>by 
practice, we use the module's artifactId as the module directory's 
name</i>).</p><p>Now, whenever a Maven command processes 
com.mycompany.app:my-app:1, that same Maven command would be ran against 
com.mycompany.app:my-module:1 as well. Furthermore, some commands (goals 
specifically) handle project aggregation differently.</p><p><a 
href="./introduction-to-the-pom.html">[top]</a></p></div></div><div 
class="section"><h4><a name="Example_4">Example 4</a></h4><div 
class="section"><h5>The Scenario<a name="The_Scenario"></a></h5><p>But what if 
we change the dire
 ctory structure to the following:</p><div class="source"><pre>.
  |-- my-module
  |   `-- pom.xml
  `-- parent

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