maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r415274 - /maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-pom.apt
Date Mon, 19 Jun 2006 10:00:51 GMT
Author: epunzalan
Date: Mon Jun 19 03:00:50 2006
New Revision: 415274

PR: MNG-1268
Submitted by: Maria Odea Ching

completed missing parts of the guide


Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-pom.apt
--- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-pom.apt (original)
+++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-pom.apt Mon Jun
19 03:00:50 2006
@@ -8,22 +8,42 @@
 Introduction to the POM
-  * You need a Project Object Model (POM)
+  * What is a POM?
-  * Explain what a POM is?
+  * Super POM
-  * Explain that the POM is the fundamental unit of work in Maven
-  * Explain the notion of the Super POM
-  * Show what a minimal POM can look like
+  * Project Inheritance
+* What is a POM?
+ A Project Object Model or POM is the fundamental unit of work in Maven. It is an xml file
that contains information 
+ about the project and configuration details used by Maven to build the project. It contains
default values for most projects.
+ Examples for this is the build directory, which is "target"; the source directory, which
is "src/main/java"; the test
+ source directory, which is "src/main/test"; and so on.
+ The POM was renamed from project.xml in Maven 1 to pom.xml in Maven 2. Instead of having
a maven.xml file that contains
+ the goals that can be executed, the goals or plugins are now configured in the pom.xml.
When executing a task or goal, Maven 
+ looks for the POM in the current directory. It reads the POM, gets the needed configuration
information, then executes the 
+ goal.  
+ Some of the configuration that can be specified in the POM are the project dependencies,
the plugins or goals that 
+ can be executed, the build profiles, and so on. Other information such as the project version,
description, developers, 
+ mailing lists and such can also be specified.
+* {{Super POM}}
+ The Super POM is Maven's default POM. All POMs extend the Super POM unless explicitly set,
meaning the configuration specified 
+ in the Super POM is inherited by the POMs you created for your projects. Let's take a look
at the Super POM and the sample minimal 
+ POM below.
-* {Super POM}
+Super POM
+Minimal POM
@@ -42,7 +62,12 @@
-* Project Inheritance
+You can see that in the minimal POM, the <repositories> were not specified. If you
build your project using the minimal POM,
+it would inherit the <repositories> configuration in the Super POM. Therefore when
Maven sees the dependencies in
+the minimal POM, it would know that these dependencies will be downloaded from
which was specified 
+in the Super POM.
+* Project Inheritance 
  Elements in the POM that are merged are the following:
@@ -58,5 +83,5 @@
- <<NOTE:>> Profile inheritance uses the same inheritance strategy as used for
the POM itself.
+ <<NOTE:>> Profile inheritance the same inheritance strategy as used for the
POM itself.

View raw message