You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2013/01/05 15:58:23 UTC
svn commit: r845127 - in /websites/staging/maven/trunk/content: ./
maven-site-1.0-site.jar pom.html
Author: buildbot
Date: Sat Jan 5 14:58:23 2013
New Revision: 845127
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
websites/staging/maven/trunk/content/pom.html
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jan 5 14:58:23 2013
@@ -1 +1 @@
-1429300
+1429301
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: websites/staging/maven/trunk/content/pom.html
==============================================================================
--- websites/staging/maven/trunk/content/pom.html (original)
+++ websites/staging/maven/trunk/content/pom.html Sat Jan 5 14:58:23 2013
@@ -1042,7 +1042,7 @@
...
</profile>
</profiles>
-</project></pre></div><p>Activation occurs when one or more of the specified criteria have been met. When the first positive result is encountered, processing stops and the profile is marked as active.</p><ul><li><b>jdk</b>: <tt>activation</tt> has a built in, Java-centric check in the <tt>jdk</tt> element. This will activate if the test is run under a jdk version number that matches the prefix given. In the above example, <tt>1.5.0_06</tt> will match. Ranges are also supported as of Maven 2.1. See the <a class="externalLink" href="http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html"> maven-enforcer-plugin</a> for more details about supported ranges.</li><li><b>os</b>: The <tt>os</tt> element can define some operating system specific properties shown above. See the <a class="externalLink" href="http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requireOS.html">maven-enforcer-plugin</a> for more details about OS values.</li><li><b>property</b>: T
he <tt>profile</tt> will activate if Maven detects a property (a value which can be dereferenced within the POM by <tt>${name}</tt>) of the corresponding <tt>name=value</tt> pair.</li><li><b>file</b>: Finally, a given filename may activate the <tt>profile</tt> by the <tt>existence</tt> of a file, or if it is <tt>missing</tt>. <b>NOTE</b>: interpolation for this element is limited to $<a name="basedir">basedir</a>, System properties and request properties.</li></ul><p>The <tt>activation</tt> element is not the only way that a <tt>profile</tt> may be activated. The <tt>settings.xml</tt> file's <tt>activeProfile</tt> element may contain the profile's <tt>id</tt>. They may also be activated explicitly through the command line via a comma separated list after the <tt>-P</tt> flag (e.g. <tt>-P test</tt>).</p><p><i>To see which profile will activate in a certain build, use the</i> <tt>maven-help-plugin</tt>.</p><div><pre>mvn help:active-profiles</pre></div></div><div class="section
"><h4><a name="The_BaseBuild_Element_Set">The BaseBuild Element Set</a> <i>(revisited)</i><a name="The_BaseBuild_Element_Set_revisited"></a></h4><p>As mentioned above, the reason for the two types of build elements reside in the fact that it does not make sense for a profile to configure build directories or extensions as it does in the top level of the POM. Reguardless of in which environment the project is built, some values will remain constant, such as the directory structure of the source code. <i>If you find your project needing to keep two sets of code for different environments, it may be prudent to investigate refactoring the project into two or more separate projects.</i></p></div></div></div><div class="section"><h2><a name="Final">Final</a></h2><p>The Maven POM is big. However, its size is also a testament to its versatility. The ability to abstract all of the aspects of a project into a single artifact is powerful, to say the least. Gone are the days of dozens o
f disparate build scripts and scattered documentation concerning each individual project. Along with Maven's other stars that make up the Maven galaxy - a well defined build lifecycle, easy to write and maintain plugins, centralized repositories, system-wide and user-based configurations, as well as the increasing number of tools to make developers' jobs easier to maintain complex projects - the POM is the large, but bright, center.</p><hr /><p>Aspects of this guide were originally published in the <a class="externalLink" href="http://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html">Maven 2 Pom Demystified</a>.</p></div>
+</project></pre></div><p>Activation occurs when one or more of the specified criteria have been met. When the first positive result is encountered, processing stops and the profile is marked as active.</p><ul><li><b>jdk</b>: <tt>activation</tt> has a built in, Java-centric check in the <tt>jdk</tt> element. This will activate if the test is run under a jdk version number that matches the prefix given. In the above example, <tt>1.5.0_06</tt> will match. Ranges are also supported as of Maven 2.1. See the <a class="externalLink" href="http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html"> maven-enforcer-plugin</a> for more details about supported ranges.</li><li><b>os</b>: The <tt>os</tt> element can define some operating system specific properties shown above. See the <a class="externalLink" href="http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requireOS.html">maven-enforcer-plugin</a> for more details about OS values.</li><li><b>property</b>: T
he <tt>profile</tt> will activate if Maven detects a property (a value which can be dereferenced within the POM by <tt>${name}</tt>) of the corresponding <tt>name=value</tt> pair.</li><li><b>file</b>: Finally, a given filename may activate the <tt>profile</tt> by the <tt>existence</tt> of a file, or if it is <tt>missing</tt>. <b>NOTE</b>: interpolation for this element is limited to <tt>${basedir}</tt>), System properties and request properties.</li></ul><p>The <tt>activation</tt> element is not the only way that a <tt>profile</tt> may be activated. The <tt>settings.xml</tt> file's <tt>activeProfile</tt> element may contain the profile's <tt>id</tt>. They may also be activated explicitly through the command line via a comma separated list after the <tt>-P</tt> flag (e.g. <tt>-P test</tt>).</p><p><i>To see which profile will activate in a certain build, use the</i> <tt>maven-help-plugin</tt>.</p><div><pre>mvn help:active-profiles</pre></div></div><div class="section"><h4><a n
ame="The_BaseBuild_Element_Set">The BaseBuild Element Set</a> <i>(revisited)</i><a name="The_BaseBuild_Element_Set_revisited"></a></h4><p>As mentioned above, the reason for the two types of build elements reside in the fact that it does not make sense for a profile to configure build directories or extensions as it does in the top level of the POM. Reguardless of in which environment the project is built, some values will remain constant, such as the directory structure of the source code. <i>If you find your project needing to keep two sets of code for different environments, it may be prudent to investigate refactoring the project into two or more separate projects.</i></p></div></div></div><div class="section"><h2><a name="Final">Final</a></h2><p>The Maven POM is big. However, its size is also a testament to its versatility. The ability to abstract all of the aspects of a project into a single artifact is powerful, to say the least. Gone are the days of dozens of disparat
e build scripts and scattered documentation concerning each individual project. Along with Maven's other stars that make up the Maven galaxy - a well defined build lifecycle, easy to write and maintain plugins, centralized repositories, system-wide and user-based configurations, as well as the increasing number of tools to make developers' jobs easier to maintain complex projects - the POM is the large, but bright, center.</p><hr /><p>Aspects of this guide were originally published in the <a class="externalLink" href="http://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html">Maven 2 Pom Demystified</a>.</p></div>
</div>
</div>
<div class="clear">