Author: svn-site-role
Date: Fri Feb 17 21:58:25 2023
New Revision: 1907722
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/configure.html
maven/website/content/maven-site-1.0-site.jar
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Fri Feb 17 21:58:25 2023
@@ -188,8 +188,14 @@ options to your Maven build every time y
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
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></section><section>
+<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>
+<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="source"><pre class="prettyprint linenums"><code>-T3
+-U
+--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>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
