You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2020/10/16 08:38:00 UTC
svn commit: r1882579 - in /maven/website/content: maven-site-1.0-site.jar
pom.html
Author: svn-site-role
Date: Fri Oct 16 08:38:00 2020
New Revision: 1882579
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/maven-site-1.0-site.jar
maven/website/content/pom.html
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: maven/website/content/pom.html
==============================================================================
--- maven/website/content/pom.html (original)
+++ maven/website/content/pom.html Fri Oct 16 08:38:00 2020
@@ -1421,7 +1421,7 @@ Display parameters as parsed by Maven (i
<ul>
<li><b>jdk</b>: <code>activation</code> has a built in, Java-centric check in the <code>jdk</code> element. This will activate if the test is run under a jdk version number that matches the prefix given. In the above example, <code>1.5.0_06</code> will match. Ranges are also supported. See the <a href="/enforcer/enforcer-rules/versionRanges.html"> maven-enforcer-plugin</a> for more details about supported ranges.</li>
<li><b>os</b>: The <code>os</code> element can define some operating system specific properties shown above. See the maven-enforcer-plugins <a class="externalLink" href="https://maven.apache.org/enforcer/enforcer-rules/requireOS.html">RequireOS Rule</a> for more details about OS values.</li>
-<li><b>property</b>: The <code>profile</code> will activate if Maven detects a property (a value which can be dereferenced within the POM by <code>${name}</code>) of the corresponding <code>name=value</code> pair.</li>
+<li><b>property</b>: The <code>profile</code> will activate if Maven detects a system property and commandline property (a value which can be dereferenced within the POM by <code>${name}</code>) of the corresponding <code>name=value</code> pair.</li>
<li><b>file</b>: Finally, a given filename may activate the <code>profile</code> by the <code>existence</code> of a file, or if it is <code>missing</code>. <b>NOTE</b>: interpolation for this element is limited to <code>${basedir}</code>, System properties and request properties.</li></ul>
<p>The <code>activation</code> element is not the only way that a <code>profile</code> may be activated. The <code>settings.xml</code> file's <code>activeProfile</code> element may contain the profile's <code>id</code>. They may also be activated explicitly through the command line via a comma separated list after the <code>-P</code> flag (e.g. <code>-P codecoverage</code>).</p>
<p><i>To see which profile will activate in a certain build, use the</i> <code>maven-help-plugin</code>.</p>