You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by an...@apache.org on 2013/04/10 10:12:36 UTC
svn commit: r1466372 -
/maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
Author: andham
Date: Wed Apr 10 08:12:36 2013
New Revision: 1466372
URL: http://svn.apache.org/r1466372
Log:
CMS commit to maven by andham
Modified:
maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
Modified: maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt?rev=1466372&r1=1466371&r2=1466372&view=diff
==============================================================================
--- maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt (original)
+++ maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt Wed Apr 10 08:12:36 2013
@@ -322,7 +322,7 @@ Introduction to the POM
+-----+
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 "pom", and for the modules section, we have the element
+ the packaging, its value was set to "pom", and for the modules section, we have the element
<<<\<module\>my-module\</module\>>>>. The value of <<<\<module\>>>> is the relative path from the com.mycompany.app:my-app:1
to com.mycompany.app:my-module:1's POM (<by practice, we use the module's artifactId as the module directory's name>).