svn commit: r927489 - in /websites/staging/maven/trunk/content: ./ maven-site-1.0-site.jar pom.html

[bu...@apache.org]

Author: buildbot
Date: Fri Oct 31 12:42:17 2014
New Revision: 927489

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 Fri Oct 31 12:42:17 2014
@@ -1 +1 @@
-1635755
+1635756

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 Fri Oct 31 12:42:17 2014
@@ -1516,7 +1516,7 @@
 <li><b>os</b>: The <tt>os</tt> element can define some operating system specific properties shown above. See the maven-enforcer-plugins <a class="externalLink" href="http://maven.apache.org/enforcer/enforcer-rules/requireOS.html">RequireOS Rule</a> for more details about OS values.</li>
 <li><b>property</b>: The <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>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 codecoverage</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>