Author: svn-site-role
Date: Sun Sep 10 22:07:38 2023
New Revision: 1912229
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/guides/introduction/introduction-to-profiles.html
maven/website/content/guides/mini/guide-configuring-maven.html
maven/website/content/guides/mini/guide-using-toolchains.html
maven/website/content/maven-site-1.0-site.jar
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 Sun
Sep 10 22:07:38 2023
@@ -241,7 +241,7 @@
...
</profile>
</profiles></pre></div>
-<p>Ranges can also be used as of Maven 2.1 (refer to the <a
href="/enforcer/enforcer-rules/versionRanges.html"> Enforcer Version Range
Syntax</a> for more information). Range values must start with either
<code>[</code> or <code>(</code> otherwise the value is interpreted as prefix.
The following honours versions 1.3, 1.4 and 1.5.</p>
+<p><a href="/enforcer/enforcer-rules/versionRanges.html"> Ranges</a> can also
be used. Range values must start with either <code>[</code> or <code>(</code>.
Otherwise, the value is interpreted as a prefix. The following honours versions
1.3, 1.4 and 1.5.</p>
<div class="verbatim source"><pre class="prettyprint linenums"><profiles>
<profile>
<activation>
@@ -346,11 +346,11 @@ mvn groupId:artifactId:goal -Ddebug=fals
...
</profile>
</profiles></pre></div>
-<p>As of Maven 2.0.9, the tags <code><exists></code> and
<code><missing></code> could be interpolated. Supported variables are
system properties like <code>${user.home}</code> and environment variables like
<code>${env.HOME}</code>. Please note that properties and values defined in the
POM itself are not available for interpolation here, e.g. the above example
activator cannot use <code>${project.build.directory}</code> but needs to
hard-code the path <code>target</code>.</p></section></section><section>
+<p>The tags <code><exists></code> and <code><missing></code> can
be interpolated. Supported variables are system properties like
<code>${user.home}</code> and environment variables like
<code>${env.HOME}</code>. Please note that properties and values defined in the
POM itself are not available for interpolation here, e.g. the above example
activator cannot use <code>${project.build.directory}</code> but needs to
hard-code the path <code>target</code>.</p></section></section><section>
<h4>Multiple conditions</h4>
<p>Different implicit activation types can be combined in one profile. The
profile is then only active if all conditions are met (since Maven 3.2.2, <a
class="externalLink"
href="https://issues.apache.org/jira/browse/MNG-4565";>MNG-4565</a>). Using the
same type more than once in the same profile is not supported (<a
class="externalLink"
href="https://issues.apache.org/jira/browse/MNG-5909";>MNG-5909</a>, <a
class="externalLink"
href="https://issues.apache.org/jira/browse/MNG-3328";>MNG-3328</a>).</p></section></section><section>
<h3>Deactivating a profile</h3>
-<p>Starting with Maven 2.0.10, one or more profiles can be deactivated using
the command line by prefixing their identifier with either the character '!' or
'-' as shown below:</p>
+<p>One or more profiles can be deactivated using the command line by prefixing
their identifier with either the character '!' or '-' as shown below:</p>
<div class="verbatim">
<pre>mvn groupId:artifactId:goal -P
!profile-1,!profile-2,!?profile-3</pre></div>
<p>or</p>
@@ -389,7 +389,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
<li><code><plugins></code></li></ul></li></ul></section><section>
<h3>POM elements outside <profiles></h3>
<p>We don't allow modification of some POM elements outside of POM-profiles
because these runtime modifications will not be distributed when the POM is
deployed to the repository system, making that person's build of that project
completely unique from others. While you can do this to some extent with the
options given for external profiles, the danger is limited. Another reason is
that this POM info is sometimes being reused from the parent POM.</p>
-<p>External files such as <code>settings.xml</code> and
<code>profiles.xml</code> also does not support elements outside the
POM-profiles. Let us take this scenario for elaboration. When the effective POM
get deployed to a remote repository, any person can pickup its info out of the
repository and use it to build a Maven project directly. Now, imagine that if
we can set profiles in dependencies, which is very important to a build, or in
any other elements outside POM-profiles in <code>settings.xml</code> then most
probably we cannot expect someone else to use that POM from the repository and
be able to build it. And we have to also think about how to share the
<code>settings.xml</code> with others. Note that too many files to configure is
very confusing and very hard to maintain. Bottom line is that since this is
build data, it should be in the POM. One of the goals in Maven 2 is to
consolidate all the information needed to run a build into a single file, or
file hierarchy which is
the POM.</p></section></section><section>
+<p>External files such as <code>settings.xml</code> and
<code>profiles.xml</code> also do not support elements outside the
POM-profiles. Let us take this scenario for elaboration. When the effective POM
is deployed to a remote repository, any person can pickup its info out of the
repository and use it to build a Maven project directly. Now, imagine that if
we can set profiles in dependencies, which is very important to a build, or in
any other elements outside POM-profiles in <code>settings.xml</code> then most
probably we cannot expect someone else to use that POM from the repository and
be able to build it. And we have to also think about how to share the
<code>settings.xml</code> with others. Note that too many files to configure
are very confusing and very hard to maintain. Bottom line is that since this is
build data, it should be in the POM.</p></section></section><section>
<h2>Profile Order</h2>
<p>All profile elements in a POM from active profiles overwrite the global
elements with the same name of the POM or extend those in case of collections.
In case multiple profiles are active in the same POM or external file, the ones
which are defined <b>later</b> take precedence over the ones defined
<b>earlier</b> (independent of their profile id and activation order).</p>
<p>Example:</p>
Modified: maven/website/content/guides/mini/guide-configuring-maven.html
==============================================================================
--- maven/website/content/guides/mini/guide-configuring-maven.html (original)
+++ maven/website/content/guides/mini/guide-configuring-maven.html Sun Sep 10
22:07:38 2023
@@ -225,9 +225,9 @@
<li>other configuration properties</li></ul>
<p>For information on this file, see the <a href="/settings.html">Settings
reference</a></p></section><section>
<h3>Security</h3>
-<p>As of Maven 2.1.0+, you can encrypt passwords in your settings file,
however you must first configure a master password. For more information on
both server passwords and the master password, see the <a
href="./guide-encryption.html">Guide to Password
Encryption</a>.</p></section><section>
+<p>You can encrypt passwords in your settings file. However, you must first
configure a master password. For more information on both server passwords and
the master password, see the <a href="./guide-encryption.html">Guide to
Password Encryption</a>.</p></section><section>
<h3>Toolchains</h3>
-<p>As of Maven 2.0.9+, you can build a project using a specific version of JDK
independent from the one Maven is running with. For more information, see the
<a href="./guide-using-toolchains.html">Guide to Using
Toolchains</a>.</p></section></section></section>
+<p>You can build a project using a specific version of JDK independent from
the one Maven is running with. For more information, see the <a
href="./guide-using-toolchains.html">Guide to Using
Toolchains</a>.</p></section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-using-toolchains.html
==============================================================================
--- maven/website/content/guides/mini/guide-using-toolchains.html (original)
+++ maven/website/content/guides/mini/guide-using-toolchains.html Sun Sep 10
22:07:38 2023
@@ -165,10 +165,10 @@
<section>
<h1>Guide to Using Toolchains</h1><section>
<h2>What is Toolchains?</h2>
-<p>The Maven Toolchains provide a way for plugins to discover what JDK (or
other tools) are to be used during the build, without the need to configure
them in each plugin nor in every <code>pom.xml</code>, or forcing a precise
location among every machine building the project.</p>
-<p>With Maven Toolchains applied to JDK toolchain, a project can now be built
using a specific version of JDK independent from the one Maven is running with.
Think how JDK versions can be set in IDEs like IDEA, NetBeans and Eclipse, or
how you can compile with an older JDK from Maven running with a recent
one.</p><section>
+<p>Maven Toolchains provide a way for plugins to discover what JDK (or other
tools) are to be used during the build, without the need to configure them in
each plugin nor in every <code>pom.xml</code>, or forcing a precise location
among every machine building the project.</p>
+<p>With Maven Toolchains applied to JDK toolchain, a project can be built
using a specific version of JDK independent from the one Maven is running with.
Think how JDK versions can be set in IDEs like IDEA, NetBeans and Eclipse, or
how you can compile with an older JDK from Maven running with a recent
one.</p><section>
<h3>Prerequisites</h3>
-<p>Toolchains will only work in Maven 2.0.9 and higher versions. For more
details about its design and implementation, please see <a class="externalLink"
href="http://cwiki.apache.org/confluence/display/MAVENOLD/Toolchains";>Toolchains</a>.</p>
+<p>For more details about Toolchains' design and implementation, see <a
class="externalLink"
href="https://cwiki.apache.org/confluence/display/MAVENOLD/Toolchains";>Toolchains</a>.</p>
<p>Below are some plugins which are toolchain-aware, with the toolchain-type
used:</p>
<table class="table table-bordered table-striped">
<tr class="a">
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
