Author: svn-site-role
Date: Wed May 29 14:01:36 2024
New Revision: 1918038
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/guides/introduction/introduction-to-profiles.html
maven/website/content/settings.html
Modified:
maven/website/content/guides/introduction/introduction-to-profiles.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-profiles.html
(original)
+++ maven/website/content/guides/introduction/introduction-to-profiles.html Wed
May 29 14:01:36 2024
@@ -191,9 +191,7 @@
<li>Per User
<p>- Defined in the <a href="/ref/current/maven-settings/settings.html">
Maven-settings</a> <code>(%USER_HOME%/.m2/settings.xml)</code>.</p></li>
<li>Global
-<p>- Defined in the <a href="/ref/current/maven-settings/settings.html">
global Maven-settings</a>
<code>(${maven.home}/conf/settings.xml)</code>.</p></li>
-<li>Profile descriptor
-<p>- a descriptor located in <a
href="/ref/2.2.1/maven-profile/profiles.html">project basedir
<code>(profiles.xml)</code></a> (no longer supported in Maven 3.0 and above;
see <a class="externalLink"
href="https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-profiles.xml";>
Maven 3 compatibility notes</a>)</p></li></ul></section><section>
+<p>- Defined in the <a href="/ref/current/maven-settings/settings.html">
global Maven-settings</a>
<code>(${maven.home}/conf/settings.xml)</code>.</p></li></ul></section><section>
<h2>Profile Inheritance</h2>
<p>The profiles are not inherited as other POM elements by child POMs. Instead
they are resolved very early by the <a
href="/ref/current/maven-model-builder/">Maven Model Builder</a> and only the
effects of active profiles are inherited (e.g. the plugins defined in the
profile). That also leads to the fact that implicit profile activation only has
an effect on the surrounding profile container but never on any other profile
(even if it has the same id).</p></section><section>
<h2>How can a profile be triggered? How does this vary according to the type
of profile being used?</h2>
@@ -327,7 +325,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<p>To activate this you would type this on the command line:</p>
<div class="verbatim">
<pre>mvn groupId:artifactId:goal -Denvironment=test</pre></div>
-<p>As of Maven 3.0, profiles in the POM can also be activated based on
properties from active profiles from the <code>settings.xml</code>.</p>
+<p>Profiles in the POM can also be activated based on properties from active
profiles from the <code>settings.xml</code>.</p>
<p><b>Note</b>: Environment variables like <code>FOO</code> are available as
properties of the form <code>env.FOO</code>. Further note that environment
variable names are normalized to all upper-case on Windows.</p>
<p>Since Maven 3.9.0 one can also evaluate the POM's packaging value by
referencing property <code>packaging</code>. This is only useful where the
profile activation is defined in a common parent POM which is reused among
multiple Maven projects. The next example will trigger the profile when a
project with packaging <code>war</code> is built:</p>
<div class="verbatim source"><pre class="prettyprint linenums"><profiles>
Modified: maven/website/content/settings.html
==============================================================================
--- maven/website/content/settings.html (original)
+++ maven/website/content/settings.html Wed May 29 14:01:36 2024
@@ -204,9 +204,9 @@ authentication information.</p>
<li>The Maven install: <code>${maven.home}/conf/settings.xml</code></li>
<li>A user's install: <code>${user.home}/.m2/settings.xml</code></li>
</ul>
-<p>The former <code>settings.xml</code> are also called global settings, the
latter
-<code>settings.xml</code> are referred to as user settings. If both files
exists,
-their contents gets merged, with the user-specific <code>settings.xml</code>
being
+<p>The former <code>settings.xml</code> is also called global settings, the
latter
+<code>settings.xml</code> is referred to as user settings. If both files exist,
+their contents get merged, with the user-specific <code>settings.xml</code>
being
dominant.</p>
<p>Tip: If you need to create user-specific settings from scratch, it's
easiest to copy the global settings from your Maven installation to your
@@ -229,14 +229,14 @@ your needs.</p>
<activeProfiles/>
</settings>
</code></pre></div>
-<p>The contents of the <code>settings.xml</code> can be interpolated using the
+<p>The contents of <code>settings.xml</code> can be interpolated using the
following expressions:</p>
<ol style="list-style-type: decimal">
-<li><code>${user.home}</code> and all other system properties <em>(since Maven
3.0)</em></li>
+<li><code>${user.home}</code> and all other system properties</li>
<li><code>${env.HOME}</code> etc. for environment variables</li>
</ol>
-<p>Note that properties defined in profiles within the
<code>settings.xml</code>
+<p>Note that properties defined in profiles within <code>settings.xml</code>
cannot be used for interpolation.</p></section></section><section>
<h2>Settings Details</h2><section>
<h3>Simple Values</h3>
