Author: svn-site-role
Date: Sun Sep 24 11:00:12 2023
New Revision: 1912518
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/configure.html
maven/website/content/docs/3.3.1/release-notes.html
maven/website/content/docs/3.3.9/release-notes.html
maven/website/content/maven-site-1.0-site.jar
maven/website/content/reference/maven-classloading.html
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Sun Sep 24 11:00:12 2023
@@ -167,8 +167,14 @@ CLI arguments. E.g., options and goals c
<p>Located in USER_HOME/.m2 the settings files is designed to contain any
configuration for Maven usage across projects.</p></section><section>
<h2><code>.mvn</code> directory:</h2>
-<p>Located within the project's top level directory, the files
<code>maven.config</code>, <code>jvm.config</code>, and
<code>extensions.xml</code>
-contain project specific configuration for running Maven.</p>
+<p>Located within the project's <strong>top level directory</strong>, the
files</p>
+<ul>
+
+<li><code>maven.config</code></li>
+<li><code>jvm.config</code></li>
+<li><code>extensions.xml</code></li>
+</ul>
+<p>contain project specific configuration for running Maven.</p>
<p>This directory is part of the project and may be checked in into your
version control.</p><section>
<h3><code>.mvn/extensions.xml</code> file:</h3>
<p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you
have other dependencies) which contains the extension and put
@@ -176,7 +182,7 @@ it manually into the <code>${MAVEN_HOME}
who likes to use this needed to change it’s installation and makes the
on-boarding for a developer much more inconvenient. The other
option was to give the path to the jar on command line via <code>mvn
-Dmaven.ext.class.path=extension.jar</code>. This has the drawback giving those
options to your Maven build every time you are calling Maven. Not very
convenient as well.</p>
-<p>From now on this can be done much more simpler and in a more Maven like
way. So you can define an
<code>${maven.projectBasedir}/.mvn/extensions.xml</code> file which looks like
the following:</p>
+<p>From now on this can be done much more simpler and in a more Maven like
way. So you can define an <code>.mvn/extensions.xml</code> file which looks
like the following:</p>
<div class="verbatim">
<pre><code class="language-xml"><extensions
xmlns="http://maven.apache.org/EXTENSIONS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -192,10 +198,10 @@ options to your Maven build every time y
<h3><code>.mvn/maven.config</code> file:</h3>
<p>It’s really hard to define a general set of options for calling the
maven command line. Starting with Maven 3.3.1+, this can be solved by
putting this
-options to a script but this can now simple being done by defining
<code>${maven.projectBasedir}/.mvn/maven.config</code> file which contains the
+options to a script but this can now simple being done by defining
<code>.mvn/maven.config</code> file which contains the
configuration options for the <code>mvn</code> command line.</p>
<p>For example things like <code>-T3 -U --fail-at-end</code>. So you only have
to call Maven just by using <code>mvn clean package</code> instead of <code>mvn
-T3 -U --fail-at-end clean package</code> and not to miss the <code>-T3 -U
--fail-at-end</code> options on every call.
-The <code>${maven.projectBasedir}/.mvn/maven.config</code> is located in the
<code>${maven.projectBasedir}/.mvn/</code> directory; also works if in the root
of a multi module build.</p>
+The <code>.mvn/maven.config</code> is located in the project's top level
<code>.mvn</code> directory also works if in the root of a multi module
build.</p>
<p><strong>NOTICE</strong> starting with Maven <strong>3.9.0</strong> each
single argument must be put in new line, so for the mentioned example your file
will have content like:</p>
<div class="verbatim">
@@ -204,7 +210,10 @@ The <code>${maven.projectBasedir}/.mvn/m
--fail-at-end
</code></pre></div></section><section>
<h3><code>.mvn/jvm.config</code> file:</h3>
-<p>Starting with Maven 3.3.1+ you can define JVM configuration via
<code>${maven.projectBasedir}/.mvn/jvm.config</code> file which means you can
define the options for your build on a per project base. This file will become
part of your project and will be checked in along with your project. So no need
anymore for <code>MAVEN_OPTS</code>, <code>.mavenrc</code> files. So for
example if you put the following JVM options into the
<code>${maven.projectBasedir}/.mvn/jvm.config</code> file</p>
+<p>Starting with Maven 3.3.1+ you can define JVM configuration via
<code>.mvn/jvm.config</code> file which means you can define the options for
your build on a per project base.
+This file will become part of your project and will be checked in along with
your project.
+So no need anymore for <code>MAVEN_OPTS</code>, <code>.mavenrc</code>
files.</p>
+<p>So for example if you put the following JVM options into the
<code>.mvn/jvm.config</code> file</p>
<div class="verbatim">
<pre><code>-Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
Modified: maven/website/content/docs/3.3.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.3.1/release-notes.html (original)
+++ maven/website/content/docs/3.3.1/release-notes.html Sun Sep 24 11:00:12 2023
@@ -211,7 +211,7 @@ more inconvenient. The other option was
options to your Maven build every time you are calling Maven. Not very
convenient as well.</p></li>
<li>
<p>From now on this can be done much more simpler and in a more Maven like
way. So
-you can define an <code>${maven.projectBasedir}/.mvn/extensions.xml</code>
file which looks
+you can define an <code>.mvn/extensions.xml</code> file in the project's top
level directory which looks
like the following:</p></li>
</ul>
@@ -232,7 +232,7 @@ like the following:</p></li>
<code>groupId</code>, <code>artifactId</code>, <code>version</code> as any
other artifact. Furthermore all
transitive dependencies of those extensions will automatically being downloaded
from your repository. So no need to create a shaded artifact anymore.</p>
-<p>An other advantage is that the <code>${maven.projectBasedir}/.mvn/</code>
+<p>An other advantage is that the <code>.mvn/</code>
directory is located in the root of your Maven project and in conseuqence
is part of your project which means you will check it in along with
your project. So everyone who checks out your project automatically
@@ -250,10 +250,10 @@ different from the repository.</p></li>
<p>It's really hard to define a general set of options for calling the maven
command line. Usually this will be solved by putting this options to a script
but this can now simple being done by defining
-<code>${maven.projectBasedir}/.mvn/maven.config</code> file which contains the
+<code>.mvn/maven.config</code> file which contains the
configuration options for the command line. For example things like <code>-T3
-U --fail-at-end</code>. So you only have to call maven just by using <code>mvn
clean package</code> instead of <code>mvn -T3 -U --fail-at-end clean
package</code> and not to miss
-the <code>-T3 -U --fail-at-end</code> options. The
<code>${maven.projectBasedir}/.mvn/maven.config</code>
-is located in the <code>${maven.projectBasedir}/.mvn/</code> directory which
is in the root
+the <code>-T3 -U --fail-at-end</code> options. The
<code>.mvn/maven.config</code>
+is located in the <code>.mvn</code> directory which is in the root
of a multi module build. This directory is part of the project and will be
checked
in into your version control. This results in being picked by everybody who
checks out the project and no need to remember to call this project
@@ -265,11 +265,11 @@ usage of <code>${user.home}/.mavenrc</co
option with the drawback of not being part of the project.</p></li>
<li>
<p>Starting with this release you can define JVM configuration via
-<code>${maven.projectBasedir}/.mvn/jvm.config</code> file which means you can
define the
+<code>.mvn/jvm.config</code> file which means you can define the
options for your build on a per project base. This file will become part of
your project and will be checked in along with your project. So no need anymore
for <code>MAVEN_OPTS</code>, <code>.mavenrc</code> files. So for example if
you put the following JVM
-options into the <code>${maven.projectBasedir}/.mvn/jvm.config</code>
file</p></li>
+options into the <code>.mvn/jvm.config</code> file</p></li>
</ul>
<div class="verbatim">
Modified: maven/website/content/docs/3.3.9/release-notes.html
==============================================================================
--- maven/website/content/docs/3.3.9/release-notes.html (original)
+++ maven/website/content/docs/3.3.9/release-notes.html Sun Sep 24 11:00:12 2023
@@ -249,7 +249,7 @@ with <a href="https://issues.apache.org/
<code>MAVEN_OPTS</code> and debugging options which has been fixed by <a
href="https://issues.apache.org/jira/browse/MNG-5813";
class="externalLink">MNG-5813</a>.</p></li>
<li>
<p>Since Maven 3.3.1 it is possible to have configurations stored on a per
project base in the
-<code>${maven.projectBasedir}/.mvn</code> directory of the project. There you
can use the <code>maven.config</code>
+<code>.mvn</code> directory of the project. There you can use the
<code>maven.config</code>
file to store command line options instead of repeating them every time you
call Maven.
In cases where this file has been empty Maven ended with a failure. This has
been fixed
with <a href="https://issues.apache.org/jira/browse/MNG-5816";
class="externalLink">MNG-5816</a>.</p></li>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: maven/website/content/reference/maven-classloading.html
==============================================================================
--- maven/website/content/reference/maven-classloading.html (original)
+++ maven/website/content/reference/maven-classloading.html Sun Sep 24 11:00:12
2023
@@ -157,7 +157,7 @@ under the License.
<p>Core Extensions is a new mechanism introduced in Maven 3.3.0 which allows
additional components to be loaded into Maven Core as part of a build
session.</p>
<p>Each core extension is loaded in a separate classloader and there is no
mechanism to share classes among core extensions. Core extensions classloaders
use Maven Core classloader as the parent and have access to both exported and
internal Maven Core classes.</p>
<p>Core extension can use <code>META-INF/maven/extension.xml</code> descriptor
to declare packages and artifacts exported by the extension. If the descriptor
is not present, no packages or artifacts are exported, but the extension can
still contribute components to Maven Core extension points.</p>
-<p>Core extensions are configured in
<code>${maven.projectBasedir}/.mvn/extensions.xml</code> configuration file.</p>
+<p>Core extensions are configured <code>.mvn/extensions.xml</code>
configuration file in the project's top level.</p>
<div class="verbatim">
<pre><code class="language-xml"><?xml version="1.0"
encoding="UTF-8"?>
