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/03/10 19:55:26 UTC
svn commit: r1875052 [1/4] - in /maven/website/content: ./
apache-resource-bundles/ developers/ developers/release/ docs/3.2.1/
docs/3.2.2/ docs/3.3.1/ docs/3.3.9/ docs/3.5.0-alpha-1/ docs/3.5.0-beta-1/
docs/3.5.0/ docs/3.5.3/ docs/3.5.4/ docs/3.6.0/ d...
Author: svn-site-role
Date: Tue Mar 10 19:55:25 2020
New Revision: 1875052
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/apache-resource-bundles/index.html
maven/website/content/community.html
maven/website/content/configure.html
maven/website/content/developers/mojo-api-specification.html
maven/website/content/developers/release/maven-core-release.html
maven/website/content/docs/3.2.1/release-notes.html
maven/website/content/docs/3.2.2/release-notes.html
maven/website/content/docs/3.3.1/release-notes.html
maven/website/content/docs/3.3.9/release-notes.html
maven/website/content/docs/3.5.0-alpha-1/release-notes.html
maven/website/content/docs/3.5.0-beta-1/release-notes.html
maven/website/content/docs/3.5.0/release-notes.html
maven/website/content/docs/3.5.3/release-notes.html
maven/website/content/docs/3.5.4/release-notes.html
maven/website/content/docs/3.6.0/release-notes.html
maven/website/content/docs/3.6.1/release-notes.html
maven/website/content/docs/3.6.3/release-notes.html
maven/website/content/faq-unoffical.html
maven/website/content/glossary.html
maven/website/content/install.html
maven/website/content/maven-ci-friendly.html
maven/website/content/maven-jsr330.html
maven/website/content/maven-logging.html
maven/website/content/maven-site-1.0-site.jar
maven/website/content/project-info.html
maven/website/content/reference/maven-classloading.html
maven/website/content/repository/index.html
maven/website/content/settings.html
Modified: maven/website/content/apache-resource-bundles/index.html
==============================================================================
--- maven/website/content/apache-resource-bundles/index.html (original)
+++ maven/website/content/apache-resource-bundles/index.html Tue Mar 10 19:55:25 2020
@@ -142,13 +142,13 @@
</p>
<ul>
-<li>META-INF/DEPENDENCIES</li>
+<li><code>META-INF/DEPENDENCIES</code></li>
-<li>META-INF/LICENSE</li>
+<li><code>META-INF/LICENSE</code></li>
-<li>META-INF/NOTICE</li>
+<li><code>META-INF/NOTICE</code></li>
-<li>META-INF/DISCLAIMER</li>
+<li><code>META-INF/DISCLAIMER</code></li>
</ul>
<div class="source"><pre class="prettyprint linenums"> <plugin>
Modified: maven/website/content/community.html
==============================================================================
--- maven/website/content/community.html (original)
+++ maven/website/content/community.html Tue Mar 10 19:55:25 2020
@@ -165,7 +165,7 @@ better for everyone.
<h4><a name="Mailing_Lists"></a>Mailing Lists</h4>
<p>Maven has a number of <a href="./mailing-lists.html">Mailing Lists</a>, and the Maven User List is specifically dedicated to answering questions about all Maven things.</p></section><section>
<h4><a name="IRC_.28Internet_Relay_Chat.29"></a>IRC (Internet Relay Chat)</h4>
-<p>Log into the #maven IRC channel on irc.freenode.net with your favorite IRC client or <a class="externalLink" href="https://webchat.freenode.net/">with web IRC chat</a>.</p></section></section></section>
+<p>Log into the <code>#maven</code> IRC channel on <code>irc.freenode.net</code> with your favorite IRC client or <a class="externalLink" href="https://webchat.freenode.net/">with web IRC chat</a>.</p></section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Tue Mar 10 19:55:25 2020
@@ -148,16 +148,16 @@ under the License.
The configuration for Apache Maven usage itself and projects built with resides
in a number of places:
<section>
-<h2><a name="MAVEN_OPTS_environment_variable:"></a>MAVEN_OPTS environment variable:</h2>
-<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to globally to Maven. E.g. JVM memory settings could be defined with the value -Xms256m -Xmx512m.</p></section><section>
-<h2><a name="settings.xml_file:"></a>settings.xml file:</h2>
+<h2><a name="MAVEN_OPTS_environment_variable:"></a><code>MAVEN_OPTS</code> environment variable:</h2>
+<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to globally to Maven. E.g. JVM memory settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
+<h2><a name="settings.xml_file:"></a><code>settings.xml</code> file:</h2>
<p>Located in USER_HOME/.m2 the settings files is designed to contain any configuration for Maven usage across projects.</p></section><section>
-<h2><a name="a.mvn_folder:"></a>.mvn folder:</h2>
-<p>Located with in the projects top level folder, the files maven.config, jvm.config, and extensions.xml contain project specific configuration for running Maven.</p>
+<h2><a name="a.mvn_folder:"></a><code>.mvn</code> folder:</h2>
+<p>Located with in the projects top level folder, the files <code>maven.config</code>, <code>jvm.config</code>, and <code>extensions.xml</code> contain project specific configuration for running Maven.</p>
<p>This folder is part of the project and may be checked in into your version control.</p><section>
-<h3><a name="a.mvn.2Fextensions.xml_file:"></a>.mvn/extensions.xml 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 it manually into the ${MAVEN_HOME}/lib/ext folder. This means you had to change the Maven installation. The consequence was that everyone 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 mvn -Dmaven.ext.class.path=extension.jar. 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 ${maven.projectBasedir}/.mvn/extensions.xml file which looks like the following:</p>
+<h3><a name="a.mvn.2Fextensions.xml_file:"></a><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 it manually into the <code>${MAVEN_HOME}/lib/ext</code> folder. This means you had to change the Maven installation. The consequence was that everyone 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>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -171,17 +171,17 @@ in a number of places:
</pre></div></div>
<p>Now you can simply use an extension by defining the usual maven coordinates groupId, artifactId, version 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></section><section>
-<h3><a name="a.mvn.2Fmaven.config_file:"></a>.mvn/maven.config 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 ${maven.projectBasedir}/.mvn/maven.config file which contains the configuration options for the mvn command line.</p>
-<p>For example things like -T3 -U --fail-at-end. So you only have to call Maven just by using mvn clean package instead of mvn -T3 -U --fail-at-end clean package and not to miss the -T3 -U --fail-at-end options on every call. The ${maven.projectBasedir}/.mvn/maven.config is located in the ${maven.projectBasedir}/.mvn/ folder; also works if in the root of a multi module build.</p></section><section>
-<h3><a name="a.mvn.2Fjvm.config_file:"></a>.mvn/jvm.config file:</h3>
-<p>Starting with Maven 3.3.1+ you can define JVM configuration via ${maven.projectBasedir}/.mvn/jvm.config 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 MAVEN_OPTS, .mavenrc files. So for example if you put the following JVM options into the ${maven.projectBasedir}/.mvn/jvm.config file</p>
+<h3><a name="a.mvn.2Fmaven.config_file:"></a><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 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> folder; also works if in the root of a multi module build.</p></section><section>
+<h3><a name="a.mvn.2Fjvm.config_file:"></a><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>
<div class="source">
<div class="source"><pre class="prettyprint linenums"> -Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
</pre></div></div>
-<p>You don’t need to remember of using this options in MAVEN_OPTS or switching between different configurations. in the end, add the following:</p></section></section><section>
+<p>You don’t need to remember of using this options in <code>MAVEN_OPTS</code> or switching between different configurations. in the end, add the following:</p></section></section><section>
<h2><a name="Other_guides"></a>Other guides</h2>
<p>The following guides contain further information to specific configuration aspects:</p>
<ul>
Modified: maven/website/content/developers/mojo-api-specification.html
==============================================================================
--- maven/website/content/developers/mojo-api-specification.html (original)
+++ maven/website/content/developers/mojo-api-specification.html Tue Mar 10 19:55:25 2020
@@ -151,27 +151,27 @@
<p>Although the requirements on Mojos are minimal by design, there are
still a very few requirements that Mojo developers must keep in mind. Basically, these Mojo requirements are embodied by the
- <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/Mojo.html">org.apache.maven.plugin.Mojo</a>
+ <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/Mojo.html"><code>org.apache.maven.plugin.Mojo</code></a>
interface, which the Mojo
must implement (or else extend its abstract base class counterpart
- <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/AbstractMojo.html">org.apache.maven.plugin.AbstractMojo</a>
+ <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/AbstractMojo.html"><code>org.apache.maven.plugin.AbstractMojo</code></a>
). This interface
guarantees the correct execution contract for the Mojo: no parameters,
void return type, and a throws clause that allows only
- <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/MojoExecutionException.html">org.apache.maven.plugin.MojoExecutionException</a>
+ <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/MojoExecutionException.html"><code>org.apache.maven.plugin.MojoExecutionException</code></a>
and its
derivatives. It also guarantees that the Mojo will have access to the
standard Maven user-feedback mechanism,
- <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/logging/Log.html">org.apache.maven.plugin.logging.Log</a>
+ <a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/logging/Log.html"><code>org.apache.maven.plugin.logging.Log</code></a>
, so the Mojo can
communicate important events to the console or other log sink.
</p>
<p>As mentioned before, each Plugin - or packaged set of Mojos - must
provide a descriptor called
- <a href="/ref/current/maven-plugin-api/plugin.html">plugin.xml</a>
+ <a href="/ref/current/maven-plugin-api/plugin.html"><code>plugin.xml</code></a>
under the path
- META-INF/maven
+ <code>META-INF/maven</code>
inside the Plugin jar file. Fortunately,
Maven also provides a set of Javadoc annotations
(named <a href="/plugin-tools/maven-plugin-tools-java/index.html">Mojo Javadoc Tags</a>),
@@ -194,15 +194,15 @@
<p>This interface forms the contract required for Mojos to interact
with the Maven infrastructure. It features an
- execute()
+ <code>execute()</code>
method, which triggers the Mojo's build-process behavior, and can
throw a
- MojoExecutionException
+ <code>MojoExecutionException</code>
if an error condition
occurs. See below for a discussion on proper use of this
- Exception
+ <code>Exception</code>
class. Also included is the
- setLog(..)
+ <code>setLog(..)</code>
method, which simply allows Maven to inject a
logging mechanism which will allow the Mojo to communicate to the
outside world through standard Maven channels.
@@ -213,27 +213,27 @@
<ul>
<li>
-
+ <code>
void setLog( org.apache.maven.plugin.logging.Log )
-
+ </code>
<p>Inject a standard Maven logging mechanism to allow this Mojo
to communicate events and feedback to the user.</p>
</li>
<li>
-
+ <code>
void execute() throws org.apache.maven.plugin.MojoExecutionException
-
+ </code>
<p>Perform whatever build-process behavior this Mojo implements.
This is the main trigger for the Mojo inside the Maven system,
and allows the Mojo to communicate fatal errors by throwing an
- instance of MojoExecutionException.
+ instance of <code>MojoExecutionException</code>.
</p>
<p>The
- MojoExecutionException (and all error
+ <code>MojoExecutionException</code> (and all error
conditions inside the Mojo) should be handled very carefully.
The simple wrapping of lower-level exceptions without providing
any indication of a user-friendly probable cause is strictly
@@ -242,7 +242,7 @@
coherent step within the Mojo's execution. Developers are then
in a much better position to diagnose the cause of any error,
and provide user-friendly feedback in the message of the
- MojoExecutionException.
+ <code>MojoExecutionException</code>.
</p>
</li>
</ul>
@@ -253,9 +253,9 @@
<p>Currently, this abstract base class simply takes care of managing
the Maven log for concrete derivations. In keeping with this, it
provides a
- protected
+ <code>protected</code>
method,
- getLog():Log
+ <code>getLog():Log</code>
,
to furnish Log access to these concrete implementations.
</p>
@@ -265,9 +265,9 @@
<ul>
<li>
-
+ <code>
public void setLog( org.apache.maven.plugin.logging.Log )
-
+ </code>
<p>
<b>[IMPLEMENTED]</b>
@@ -278,7 +278,7 @@
</li>
<li>
- protected Log getLog()
+ <code>protected Log getLog()</code>
<p>
<b>[IMPLEMENTED]</b>
@@ -289,9 +289,9 @@
</li>
<li>
-
+ <code>
void execute() throws org.apache.maven.plugin.MojoExecutionException
-
+ </code>
<p>
<b>[ABSTRACT]</b>
@@ -299,7 +299,7 @@
<p>Perform whatever build-process behavior this Mojo implements.
See the documentation for
- Mojo
+ <code>Mojo</code>
above for more
information.
</p>
@@ -312,15 +312,15 @@
<p>This interface supplies the API for providing feedback to the user
from the Mojo, using standard Maven channels. There should be no big
surprises here, although you may notice that the methods accept
- java.lang.CharSequence
+ <code>java.lang.CharSequence</code>
rather than
- java.lang.String
+ <code>java.lang.String</code>
. This is provided mainly as a
convenience, to enable developers to pass things like
- StringBuffer
+ <code>StringBuffer</code>
directly into the logger, rather than
formatting first by calling
- toString()
+ <code>toString()</code>
.
</p>
<section><section><section>
@@ -329,7 +329,7 @@
<ul>
<li>
- void debug( java.lang.CharSequence )
+ <code>void debug( java.lang.CharSequence )</code>
<p>Send a message to the user in the
<b>debug</b>
@@ -338,9 +338,9 @@
</li>
<li>
-
+ <code>
void debug( java.lang.CharSequence, java.lang.Throwable )
-
+ </code>
<p>Send a message (and accompanying exception) to the user in the
<b>debug</b>
@@ -350,7 +350,7 @@
</li>
<li>
- void debug( java.lang.Throwable )
+ <code>void debug( java.lang.Throwable )</code>
<p>Send an exception to the user in the
<b>debug</b>
@@ -361,7 +361,7 @@
</li>
<li>
- void info( java.lang.CharSequence )
+ <code>void info( java.lang.CharSequence )</code>
<p>Send a message to the user in the
<b>info</b>
@@ -370,9 +370,9 @@
</li>
<li>
-
+ <code>
void info( java.lang.CharSequence, java.lang.Throwable )
-
+ </code>
<p>Send a message (and accompanying exception) to the user in the
<b>info</b>
@@ -382,7 +382,7 @@
</li>
<li>
- void info( java.lang.CharSequence )
+ <code>void info( java.lang.CharSequence )</code>
<p>Send an exception to the user in the
<b>info</b>
@@ -393,7 +393,7 @@
</li>
<li>
- void warn( java.lang.CharSequence )
+ <code>void warn( java.lang.CharSequence )</code>
<p>Send a message to the user in the
<b>warn</b>
@@ -402,9 +402,9 @@
</li>
<li>
-
+ <code>
void warn( java.lang.CharSequence, java.lang.Throwable )
-
+ </code>
<p>Send a message (and accompanying exception) to the user in the
<b>warn</b>
@@ -414,7 +414,7 @@
</li>
<li>
- void warn( java.lang.CharSequence )
+ <code>void warn( java.lang.CharSequence )</code>
<p>Send an exception to the user in the
<b>warn</b>
@@ -425,7 +425,7 @@
</li>
<li>
- void error( java.lang.CharSequence )
+ <code>void error( java.lang.CharSequence )</code>
<p>Send a message to the user in the
<b>error</b>
@@ -434,9 +434,9 @@
</li>
<li>
-
+ <code>
void error( java.lang.CharSequence, java.lang.Throwable )
-
+ </code>
<p>Send a message (and accompanying exception) to the user in the
<b>error</b>
@@ -446,7 +446,7 @@
</li>
<li>
- void error( java.lang.CharSequence )
+ <code>void error( java.lang.CharSequence )</code>
<p>Send an exception to the user in the
<b>error</b>
@@ -490,7 +490,7 @@
<p>The plugin descriptor (see <a href="/ref/current/maven-plugin-api/plugin.html">descriptor reference</a>)
must be provided in a jar resource with the path:
- META-INF/maven/plugin.xml, and it must contain the following:
+ <code>META-INF/maven/plugin.xml</code>, and it must contain the following:
</p>
<table border="0" class="table table-striped">
@@ -506,35 +506,35 @@
<tr class="b">
-<td>mojos</td>
+<td><code>mojos</code></td>
<td>Yes</td>
<td>Descriptors for each Mojo provided by the plugin, each inside a
- <b>mojo</b>
+ <b><code>mojo</code></b>
sub-element. Mojo descriptors are covered in detail
below. Obviously, a plugin without any declared Mojos doesn't
make sense, so the
- <b>mojos</b>
+ <b><code>mojos</code></b>
element is required, along with
at least one
- <b>mojo</b>
+ <b><code>mojo</code></b>
sub-element.
</td>
</tr>
<tr class="a">
-<td>dependencies</td>
+<td><code>dependencies</code></td>
<td>Yes</td>
<td>A set of dependencies which the plugin requires in order to
function. Each dependency is provided inside a
- <b>dependency</b>
+ <b><code>dependency</code></b>
sub-element. Dependency specifications are covered below. Since
all plugins must have a dependency on
- maven-plugin-api
+ <code>maven-plugin-api</code>
, this element is effectively
required.
<i>Using the plugin toolset, these dependencies can be
@@ -562,9 +562,9 @@
<tr class="b">
-<td>aggregator</td>
+<td><code>aggregator</code></td>
-<td>@aggregator</td>
+<td><code>@aggregator</code></td>
<td>No</td>
@@ -574,9 +574,9 @@
<tr class="a">
-<td>configurator</td>
+<td><code>configurator</code></td>
-<td>@configurator <roleHint></td>
+<td><code>@configurator <roleHint></code></td>
<td>No</td>
@@ -590,18 +590,18 @@
<tr class="b">
-<td>execute</td>
+<td><code>execute</code></td>
<td>
<ul>
-<li>@execute phase="<phaseName>"
- lifecycle="<lifecycleId>"</li>
+<li><code>@execute phase="<phaseName>"
+ lifecycle="<lifecycleId>"</code></li>
-<li>@execute phase="<phaseName>"</li>
+<li><code>@execute phase="<phaseName>"</code></li>
-<li>@execute goal="<goalName>"</li>
+<li><code>@execute goal="<goalName>"</code></li>
</ul>
</td>
@@ -610,16 +610,16 @@
<td>When this goal is invoked, it will first invoke a parallel lifecycle, ending at the given
phase. If a goal is provided instead of a phase, that goal will be executed in isolation.
The execution of either will not affect the current project, but instead make available the
- ${executedProject} expression if required. An alternate lifecycle can also be
+ <code>${executedProject}</code> expression if required. An alternate lifecycle can also be
provided: for more information see the documentation on the
<a href="../guides/introduction/introduction-to-the-lifecycle.html">build lifecycle</a>.</td>
</tr>
<tr class="a">
-<td>executionStrategy</td>
+<td><code>executionStrategy</code></td>
-<td>@executionStrategy <strategy></td>
+<td><code>@executionStrategy <strategy></code></td>
<td>No</td>
@@ -630,9 +630,9 @@
<tr class="b">
-<td>goal</td>
+<td><code>goal</code></td>
-<td>@goal <goalName></td>
+<td><code>@goal <goalName></code></td>
<td>Yes</td>
@@ -642,47 +642,47 @@
<tr class="a">
-<td>inheritByDefault</td>
+<td><code>inheritByDefault</code></td>
-<td>@inheritByDefault <true|false></td>
+<td><code>@inheritByDefault <true|false></code></td>
-<td>No. Default: true</td>
+<td>No. Default: <code>true</code></td>
<td>Specify that the Mojo is inherited.</td>
</tr>
<tr class="b">
-<td>instantiationStrategy</td>
+<td><code>instantiationStrategy</code></td>
-<td>@instantiationStrategy <per-lookup></td>
+<td><code>@instantiationStrategy <per-lookup></code></td>
-<td>No. Default: per-lookup</td>
+<td>No. Default: <code>per-lookup</code></td>
<td>Specify the instantiation strategy.</td>
</tr>
<tr class="a">
-<td>phase</td>
+<td><code>phase</code></td>
-<td>@phase <phaseName></td>
+<td><code>@phase <phaseName></code></td>
<td>No</td>
<td>
Defines a default phase to bind a mojo execution to if the user does not explicitly set a phase in the POM.
<i>Note:</i> This annotation will not automagically make a mojo run when the plugin declaration is added
- to the POM. It merely enables the user to omit the <phase> element from the surrounding
- <execution> element.
+ to the POM. It merely enables the user to omit the <code><phase></code> element from the surrounding
+ <code><execution></code> element.
</td>
</tr>
<tr class="b">
-<td>requiresDependencyResolution</td>
+<td><code>requiresDependencyResolution</code></td>
-<td>@requiresDependencyResolution <requiredClassPath></td>
+<td><code>@requiresDependencyResolution <requiredClassPath></code></td>
<td>No</td>
@@ -710,7 +710,7 @@
<tr class="b">
-<td>compile</td>
+<td><code>compile</code></td>
<td>X</td>
@@ -725,7 +725,7 @@
<tr class="a">
-<td>runtime</td>
+<td><code>runtime</code></td>
<td>-</td>
@@ -740,7 +740,7 @@
<tr class="b">
-<td>compile+runtime (since Maven 3.0)</td>
+<td><code>compile+runtime</code> (since Maven 3.0)</td>
<td>X</td>
@@ -755,7 +755,7 @@
<tr class="a">
-<td>test</td>
+<td><code>test</code></td>
<td>X</td>
@@ -768,7 +768,7 @@
<td>X</td>
</tr>
</table>
- If this annotation is present but no scope is specified, the scope defaults to runtime. If
+ If this annotation is present but no scope is specified, the scope defaults to <code>runtime</code>. If
the annotation is not present at all, the mojo must not make any assumptions about the artifacts associated
with a Maven project.
</td>
@@ -776,20 +776,20 @@
<tr class="a">
-<td>requiresDependencyCollection</td>
+<td><code>requiresDependencyCollection</code></td>
-<td>@requiresDependencyCollection <requiredClassPath></td>
+<td><code>@requiresDependencyCollection <requiredClassPath></code></td>
<td>No</td>
<td>
Flags this mojo as requiring information about the dependencies that would make up the specified class path.
- As the name suggests, this annotation is similar to @requiresDependencyResolution and supports
+ As the name suggests, this annotation is similar to <code>@requiresDependencyResolution</code> and supports
the same values for <i><requiredClassPath></i>. The important difference is that this annotation will
not resolve the files for the dependencies, i.e. the artifacts associated with a Maven project can lack a
file. As such, this annotation is meant for mojos that only want to analyze the set of transitive
dependencies, in particular during early lifecycle phases where full dependency resolution might fail due to
- projects which haven't been built yet. A mojo may use both this annotation and @requiresDependencyResolution
+ projects which haven't been built yet. A mojo may use both this annotation and <code>@requiresDependencyResolution</code>
at the same time. The resolution state of any dependency that is collected but not requested to be resolved
is undefined. Since Maven 3.0.
</td>
@@ -797,60 +797,60 @@
<tr class="b">
-<td>requiresDirectInvocation</td>
+<td><code>requiresDirectInvocation</code></td>
-<td>@requiresDirectInvocation <true|false></td>
+<td><code>@requiresDirectInvocation <true|false></code></td>
-<td>No. Default: false</td>
+<td>No. Default: <code>false</code></td>
<td>Flags this Mojo to be invoke directly.</td>
</tr>
<tr class="a">
-<td>requiresOnline</td>
+<td><code>requiresOnline</code></td>
-<td>@requiresOnline <true|false></td>
+<td><code>@requiresOnline <true|false></code></td>
-<td>No. Default: false</td>
+<td>No. Default: <code>false</code></td>
<td>Flags this Mojo to require online mode for its operation.</td>
</tr>
<tr class="b">
-<td>requiresProject</td>
+<td><code>requiresProject</code></td>
-<td>@requiresProject <true|false></td>
+<td><code>@requiresProject <true|false></code></td>
-<td>No. Default: true</td>
+<td>No. Default: <code>true</code></td>
<td>Flags this Mojo to run inside of a project.</td>
</tr>
<tr class="a">
-<td>requiresReports</td>
+<td><code>requiresReports</code></td>
-<td>@requiresReports <true|false></td>
+<td><code>@requiresReports <true|false></code></td>
-<td>No. Default: false</td>
+<td>No. Default: <code>false</code></td>
<td>Flags this Mojo to require reports. Unsupported since Maven 3.0.</td>
</tr>
<tr class="b">
-<td>threadSafe</td>
+<td><code>threadSafe</code></td>
-<td>@threadSafe <true|false></td>
+<td><code>@threadSafe <true|false></code></td>
-<td>No. Default: false</td>
+<td>No. Default: <code>false</code></td>
<td>
Marks this mojo as being thread-safe, i.e. the mojo safely supports concurrent execution during parallel builds.
Mojos without this annotation will make Maven output a warning when used during a parallel build session.
- The short-hand notation @threadSafe without a tag value is equivalent to @threadSafe true.
+ The short-hand notation <code>@threadSafe</code> without a tag value is equivalent to <code>@threadSafe true</code>.
Since Maven 3.0.
</td>
</tr>
@@ -859,7 +859,7 @@
<tr class="a">
-<td>description</td>
+<td><code>description</code></td>
<td>none (detected)</td>
@@ -874,7 +874,7 @@
<tr class="b">
-<td>implementation</td>
+<td><code>implementation</code></td>
<td>none (detected)</td>
@@ -885,11 +885,11 @@
<tr class="a">
-<td>language</td>
+<td><code>language</code></td>
<td>none (detected)</td>
-<td>No. Default: java</td>
+<td>No. Default: <code>java</code></td>
<td>The implementation language for this Mojo (Java, beanshell, etc.).</td>
</tr>
@@ -898,9 +898,9 @@
<tr class="b">
-<td>deprecated</td>
+<td><code>deprecated</code></td>
-<td>@deprecated <deprecated-text></td>
+<td><code>@deprecated <deprecated-text></code></td>
<td>No</td>
@@ -911,9 +911,9 @@
<tr class="a">
-<td>since</td>
+<td><code>since</code></td>
-<td>@since <since-text></td>
+<td><code>@since <since-text></code></td>
<td>No</td>
@@ -958,9 +958,9 @@
<tr class="b">
-<td>alias</td>
+<td><code>alias</code></td>
-<td>@parameter alias="myAlias"</td>
+<td><code>@parameter alias="myAlias"</code></td>
<td>No</td>
@@ -971,31 +971,31 @@
<tr class="a">
-<td>configuration</td>
+<td><code>configuration</code></td>
-<td>@component role="..." roleHint="..."</td>
+<td><code>@component role="..." roleHint="..."</code></td>
<td>No</td>
<td>Populates the field with an instance of a Plexus component. This is like declaring a
<i>requirement</i> in a Plexus component. The default requirement will have a role equal
to the declared type of the field, and will use the role hint "default". You can customise
- either of these by providing a role and/or roleHint parameter.
+ either of these by providing a <code>role</code> and/or <code>roleHint</code> parameter.
<i>e.g.</i>
- @component role="org.apache.maven.artifact.ArtifactHandler"
- roleHint="ear". <b>Note:</b> This is identical to the deprecated
- form of parameter: @parameter
- expression="${component.yourpackage.YourComponentClass#roleHint}". </td>
+ <code>@component role="org.apache.maven.artifact.ArtifactHandler"
+ roleHint="ear"</code>. <b>Note:</b> This is identical to the deprecated
+ form of parameter: <code>@parameter
+ expression="${component.yourpackage.YourComponentClass#roleHint}"</code>. </td>
</tr>
<tr class="b">
-<td>configuration</td>
+<td><code>configuration</code></td>
-<td>maven-plugin-plugin 2.x:<br />@parameter expression="${aSystemProperty}"
- default-value="${anExpression}"<br /><br />
- maven-plugin-plugin 3.x:<br />@parameter property="aSystemProperty"
- default-value="${anExpression}"</td>
+<td>maven-plugin-plugin 2.x:<br /><code>@parameter expression="${aSystemProperty}"
+ default-value="${anExpression}"</code><br /><br />
+ maven-plugin-plugin 3.x:<br /><code>@parameter property="aSystemProperty"
+ default-value="${anExpression}"</code></td>
<td>No</td>
@@ -1003,18 +1003,18 @@
<p>Specifies the expressions used to calculate the value to be injected into this parameter of
the Mojo at buildtime.</p>
-<p>The expression given by default-value is commonly used to refer to
- specific elements in the POM, such as ${project.resources}, which refers to the list of
+<p>The expression given by <code>default-value</code> is commonly used to refer to
+ specific elements in the POM, such as <code>${project.resources}</code>, which refers to the list of
resources meant to accompany the classes in the resulting JAR file. Of course, the default value need not
- be an expression but can also be a simple constant like true or 1.5. And for
- parameters of type String one can mix expressions with literal values, e.g.
- ${project.artifactId}-${project.version}-special.</p>
+ be an expression but can also be a simple constant like <code>true</code> or <code>1.5</code>. And for
+ parameters of type <code>String</code> one can mix expressions with literal values, e.g.
+ <code>${project.artifactId}-${project.version}-special</code>.</p>
-<p>The system property given by property in maven-plugin-plugin 3.x or expression
+<p>The system property given by <code>property</code> in maven-plugin-plugin 3.x or <code>expression</code>
in maven-plugin-plugin 2.x
- enables users to override the default value from the command line via -DaSystemProperty=value.</p>
+ enables users to override the default value from the command line via <code>-DaSystemProperty=value</code>.</p>
-<p><i>NOTE: If neither default-value nor property or expression are specified,
+<p><i>NOTE: If neither <code>default-value</code> nor <code>property</code> or <code>expression</code> are specified,
the parameter can only be configured from the POM. The use of '${' and '}' in default value is required to delimit actual expressions
which may be evaluated.</i></p>
</td>
@@ -1022,9 +1022,9 @@
<tr class="a">
-<td>editable</td>
+<td><code>editable</code></td>
-<td>@readonly</td>
+<td><code>@readonly</code></td>
<td>No</td>
@@ -1042,9 +1042,9 @@
<tr class="b">
-<td>required</td>
+<td><code>required</code></td>
-<td>@required</td>
+<td><code>@required</code></td>
<td>No</td>
@@ -1059,7 +1059,7 @@
<tr class="a">
-<td>description</td>
+<td><code>description</code></td>
<td>none (detected)</td>
@@ -1074,7 +1074,7 @@
<tr class="b">
-<td>name</td>
+<td><code>name</code></td>
<td>none (detected)</td>
@@ -1088,7 +1088,7 @@
<tr class="a">
-<td>type</td>
+<td><code>type</code></td>
<td>none (detected)</td>
@@ -1105,9 +1105,9 @@
<tr class="b">
-<td>deprecated</td>
+<td><code>deprecated</code></td>
-<td>@deprecated <deprecated-text></td>
+<td><code>@deprecated <deprecated-text></code></td>
<td>No</td>
@@ -1118,9 +1118,9 @@
<tr class="a">
-<td>since</td>
+<td><code>since</code></td>
-<td>@since <since-text></td>
+<td><code>@since <since-text></code></td>
<td>No</td>
@@ -1184,9 +1184,9 @@
<td>Yes</td>
<td>
- <packaging>
+ <code><packaging>
maven-plugin
- </packaging>
+ </packaging></code>
</td>
<td>The POM must declare a packaging element which describes this
@@ -1200,16 +1200,16 @@
<td>No</td>
<td>
- <scriptSourceDirectory>
+ <code><scriptSourceDirectory>
src/main/scripts
- </scriptSourceDirectory>
+ </scriptSourceDirectory></code>
</td>
<td>In the case of script-based Mojos (which are not covered in
detail within this document), the POM must include an additional
element to distinguish script sources from (optional) Java
- supporting classes. This element is scriptSourceDirectory,
- inside the build section. This directory is included in the list
+ supporting classes. This element is <code>scriptSourceDirectory</code>,
+ inside the <code>build</code> section. This directory is included in the list
of resources which accompany any compiled code in the resulting
artifact. It is specified separately from the resources in the
build section to denote its special status as an alternate source
@@ -1237,7 +1237,7 @@
<ol style="list-style-type: decimal">
<li>Download <a href="./maven.xml">this file</a>,
- and place it in $USER_HOME/.IntelliJIdea/config/templates</li>
+ and place it in <code>$USER_HOME/.IntelliJIdea/config/templates</code></li>
<li>(re)startup IntelliJ IDEA (templates are loaded on startup)</li>
Modified: maven/website/content/developers/release/maven-core-release.html
==============================================================================
--- maven/website/content/developers/release/maven-core-release.html (original)
+++ maven/website/content/developers/release/maven-core-release.html Tue Mar 10 19:55:25 2020
@@ -156,12 +156,12 @@ under the License.
-->
Maven differs slightly in its release process due to several extra steps.
-<p>The goal is to commit candidate release to svn tree <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/maven/maven-3">https://dist.apache.org/repos/dist/dev/maven/maven-3</a>/$VERSION. Then once the vote passed, svn move to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/maven-3">https://dist.apache.org/repos/dist/release/maven/maven-3</a>/$VERSION.</p>
+<p>The goal is to commit candidate release to svn tree <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/maven/maven-3">https://dist.apache.org/repos/dist/dev/maven/maven-3</a>/<code>$VERSION</code>. Then once the vote passed, svn move to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/maven-3">https://dist.apache.org/repos/dist/release/maven/maven-3</a>/<code>$VERSION</code>.</p>
<p>The tree directory is:</p>
<ul>
-<li><a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/maven-3/">https://dist.apache.org/repos/dist/release/maven/maven-3/</a>$VERSION/binaries</li>
-<li><a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/maven-3/">https://dist.apache.org/repos/dist/release/maven/maven-3/</a>$VERSION/source (notice: singular…)</li>
+<li><a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/maven-3/">https://dist.apache.org/repos/dist/release/maven/maven-3/</a><code>$VERSION</code>/binaries</li>
+<li><a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/maven-3/">https://dist.apache.org/repos/dist/release/maven/maven-3/</a><code>$VERSION</code>/source (notice: singular…)</li>
</ul>
<p>Note that the policy for failed releases is to move forward with a new version. The tag that produced the failed released is left in place for posterity. So if the release of, say, 3.2.4 fails then we move forward with 3.2.5.</p><section>
<h3><a name="Produce_Release_Candidates"></a>Produce Release Candidates</h3>
@@ -191,15 +191,15 @@ Maven differs slightly in its release pr
<p>Note that release notes can be created and checked in, but other changes should not be checked in as it can be deployed ‘live’ at any time.</p>
<ul>
-<li>For 3.x: update the versions3x, currentStableVersion and currentStableReleaseDate properties in pom.xml</li>
+<li>For 3.x: update the <code>versions3x</code>, <code>currentStableVersion</code> and <code>currentStableReleaseDate</code> properties in <code>pom.xml</code></li>
</ul>
<p>Next, create the release notes:</p>
<ul>
-<li>create content/markdown/docs/$version</li>
-<li>create content/markdowndocs/$version/release-notes.md (see other versions for an example)</li>
+<li>create <code>content/markdown/docs/$version</code></li>
+<li>create <code>content/markdowndocs/$version/release-notes.md</code> (see other versions for an example)</li>
</ul>
-<p>Next, update release history content/markdown/docs/history.md.vm.</p>
+<p>Next, update release history <code>content/markdown/docs/history.md.vm</code>.</p>
<p>Only deploy the site once the release is present on the mirrors, and the reference documentation has been deployed to <a href="/ref">/ref/</a>.</p></section><section>
<h4><a name="Stage_the_Latest_Documentation"></a>Stage the Latest Documentation</h4>
<p>Once the release is prepared, but before the release vote, the site needs to be staged.</p>
@@ -222,14 +222,14 @@ mvn scm-publish:publish-scm
</section><section>
<h4><a name="Deploy_the_Latest_Documentation_to_Target_Versioned_Location"></a>Deploy the Latest Documentation to Target Versioned Location</h4>
<p>The reference documentation for Maven core source code references and API docs has been staged in a previous step: now it needs to be deployed to its dedicated directory before deploying the web site pointing to the new version.</p>
-<p>This consists in copying in website svn tree the staging /ref/3-LATEST directory to final /ref/$VERSION.</p>
+<p>This consists in copying in website svn tree the staging /ref/3-LATEST directory to final /ref/<code>$VERSION</code>.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">svn cp https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST https://svn.apache.org/repos/asf/maven/website/components/ref/$VERSION
</pre></div></div>
</section></section><section>
-<h3><a name="Information_on_.2Fref.2Fcurrent_mechanism"></a>Information on /ref/current mechanism</h3>
-<p>The redirection from /ref/current to actual Maven version reference is done through .htaccess published in site.</p><section>
+<h3><a name="Information_on_.2Fref.2Fcurrent_mechanism"></a>Information on <code>/ref/current</code> mechanism</h3>
+<p>The redirection from <code>/ref/current</code> to actual Maven version reference is done through <code>.htaccess</code> published in site.</p><section>
<h4><a name="Deploying_the_Release_Website"></a>Deploying the Release Website</h4>
<p>Once both of the above have synced to the main site and a suitable number of mirrors, proceed to update the web site and produce the announcement.</p>
<p>Commit your changes and then <a href="../website/deploy-maven-website.html">deploy the main Maven site</a>.</p></section><section>
Modified: maven/website/content/docs/3.2.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.2.1/release-notes.html (original)
+++ maven/website/content/docs/3.2.1/release-notes.html Tue Mar 10 19:55:25 2020
@@ -185,17 +185,17 @@
</pre></div></div>
</section><section>
<h3><a name="Reactor_changes"></a>Reactor changes</h3>
-<p>The Maven reactor is now pluggable (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5578">MNG-5578</a>). This feature required the introduction of a new custom Guice scope called @SessionScoped as we need to inject the MavenSession into the reactor right after the creation the MavenSession and before the execution of the build. The reactor behaves as a special type of artifact repository that provides the current behaviour users expect when building multi-module projects. New implementations can provide different semantics which can potentially provide new ways for multi-module projects to build, or to fix/add new features like resolving test JARs properly from the reactor. Now that the implementation is pluggable we can always default to the existing behaviour and allow people to try new behavior with a feature toggle.</p>
-<p>The reactor now limits the projects that are exposed internally when --projects is used (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5557">MNG-5557</a>). What happened previously is that all the projects in the reactor would still be available for resolution even if you restricted the number of projects being built using --projects. This behaviour is now explicit: what you specify using --projects is what you will build and resolve against, if a project you need is not present in the constrained set the local repository will be consulted. There are cases where you may still want access to the projects that are normally part of the build but not currently being built, and those projects are tracked (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5582">MNG-5582</a>) and available in the MavenSession. It is also now possible to exclude projects from the reactor when using the -am and -amd options (<a class="externalLink" href="htt
ps://issues.apache.org/jira/browse/MNG-5230">MNG-5230</a>). If you select a project to build and its dependents (-amd) you can exclude one or more of the dependents with a command like the following: mvn -amd --projects foo,bar,!dependent-of-bar.</p>
+<p>The Maven reactor is now pluggable (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5578">MNG-5578</a>). This feature required the introduction of a new custom Guice scope called <code>@SessionScoped</code> as we need to inject the <code>MavenSession</code> into the reactor right after the creation the <code>MavenSession</code> and before the execution of the build. The reactor behaves as a special type of artifact repository that provides the current behaviour users expect when building multi-module projects. New implementations can provide different semantics which can potentially provide new ways for multi-module projects to build, or to fix/add new features like resolving test JARs properly from the reactor. Now that the implementation is pluggable we can always default to the existing behaviour and allow people to try new behavior with a feature toggle.</p>
+<p>The reactor now limits the projects that are exposed internally when <code>--projects</code> is used (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5557">MNG-5557</a>). What happened previously is that all the projects in the reactor would still be available for resolution even if you restricted the number of projects being built using <code>--projects</code>. This behaviour is now explicit: what you specify using <code>--projects</code> is what you will build and resolve against, if a project you need is not present in the constrained set the local repository will be consulted. There are cases where you may still want access to the projects that are normally part of the build but not currently being built, and those projects are tracked (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5582">MNG-5582</a>) and available in the <code>MavenSession</code>. It is also now possible to exclude projects from the reactor when using the <co
de>-am</code> and <code>-amd</code> options (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5230">MNG-5230</a>). If you select a project to build and its dependents (<code>-amd</code>) you can exclude one or more of the dependents with a command like the following: <code>mvn -amd --projects foo,bar,!dependent-of-bar</code>.</p>
<p>These combined changes above will allow us to make new implementation of the Maven reactor with improved/different behaviour. For example, this could potentially allow you to step into a directory and run Maven and have Maven pick up the projects surrounding the project you’re building instead of going to local repository. We can experiment with different implementations and let users toggle between them until we ultimately decide on the right behaviour. Lots of user complain about the behaviour of the reactor and this allows stepwise improvement.</p></section><section>
<h3><a name="AbstractMavenLifecycleParticipant_changes_.28MNG-5389.29"></a>AbstractMavenLifecycleParticipant changes (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5389">MNG-5389</a>)</h3>
-<p>The AbstractMavenLifecycleParticipant has a new afterSessionEnd() method which will be executed when the build is complete. This feature was added to account for end of build deployment in a parallel build. The current logic employed in many plugins is to look for the last project in the array of projects that are in the reactor, but during a parallel build there is no guaranteed execution order and breaks in plugins which assume there is. There needs to be a way to execute logic when the build is definitively complete and AbstractMavenLifecycleParticipant.afterSessionEnd() provides this.</p></section><section>
+<p>The <code>AbstractMavenLifecycleParticipant</code> has a new <code>afterSessionEnd()</code> method which will be executed when the build is complete. This feature was added to account for end of build deployment in a parallel build. The current logic employed in many plugins is to look for the last project in the array of projects that are in the reactor, but during a parallel build there is no guaranteed execution order and breaks in plugins which assume there is. There needs to be a way to execute logic when the build is definitively complete and <code>AbstractMavenLifecycleParticipant.afterSessionEnd()</code> provides this.</p></section><section>
<h3><a name="New_Builder_interface_.28MNG-5575.29"></a>New Builder interface (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5575">MNG-5575</a>)</h3>
<p>There is a new Builder interface which classes can implement to encapsulate a strategy for building projects. The existing strategies for building Maven serially and in parallel are now Builder implementations. It’s now possible for others to implement additional strategies for building projects. This is a provisional interface and may change in the near future but will stabilize by Maven 4.0.0.</p></section><section>
<h3><a name="Continuous_delivery_friendly_versions_.28MNG-5576.29"></a>Continuous delivery friendly versions (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5576">MNG-5576</a>)</h3>
-<p>A simple change to prevent Maven from emitting warnings about versions with property expressions. Allowed property expressions in versions include ${revision}, ${changelist}, and ${sha1}. These properties can be set externally, but eventually a mechanism will be created in Maven where these properties can be injected in a standard way. For example you may want to glean the current Git revision and inject that value into ${sha1}. This is by no means a complete solution for continuous delivery but is a step in the right direction.</p></section><section>
+<p>A simple change to prevent Maven from emitting warnings about versions with property expressions. Allowed property expressions in versions include <code>${revision}</code>, <code>${changelist}</code>, and <code>${sha1}</code>. These properties can be set externally, but eventually a mechanism will be created in Maven where these properties can be injected in a standard way. For example you may want to glean the current Git revision and inject that value into ${sha1}. This is by no means a complete solution for continuous delivery but is a step in the right direction.</p></section><section>
<h3><a name="Custom_lifecycle_mapping_.28MNG-5581.29"></a>Custom lifecycle mapping (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5581">MNG-5581</a>)</h3>
-<p>Implementations of the new LifecycleMappingDelegate interface can create custom lifecycles. The delegate has access to the existing lifecycles so it can create projections of existing lifecycles or create completely new ones. A simple example might be to create a lifecycle called test-only which might extract only the Surefire execution from the standard lifecycle and execute it.</p></section></section><section>
+<p>Implementations of the new <code>LifecycleMappingDelegate</code> interface can create custom lifecycles. The delegate has access to the existing lifecycles so it can create projections of existing lifecycles or create completely new ones. A simple example might be to create a lifecycle called <code>test-only</code> which might extract only the Surefire execution from the standard lifecycle and execute it.</p></section></section><section>
<h2><a name="Complete_Release_Notes"></a>Complete Release Notes</h2>
<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></section>
</main>
Modified: maven/website/content/docs/3.2.2/release-notes.html
==============================================================================
--- maven/website/content/docs/3.2.2/release-notes.html (original)
+++ maven/website/content/docs/3.2.2/release-notes.html Tue Mar 10 19:55:25 2020
@@ -212,7 +212,7 @@
<h3><a name="a.24.7Bmaven.build.timestamp.7D_should_use_UTC_instead_of_local_timezone_.28or_be_configurable.29_.28MNG-5452.29"></a>${maven.build.timestamp} should use UTC instead of local timezone (or be configurable) (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5452">MNG-5452</a>)</h3>
<p>This provides a standard way creating a build time stamp, and allows better interoperability with systems that also employ UTC for timestamps like Eclipse Tycho.</p></section><section>
<h3><a name="a.24.7Bmaven.build.timestamp.7D_uses_incorrect_ISO_datetime_separator_.28MNG-5647.29"></a>${maven.build.timestamp} uses incorrect ISO datetime separator (<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5647">MNG-5647</a>)</h3>
-<p>The default format has been changed to standard ISO 8601 (yyyy-MM-dd'T'HH:mm:ss'Z') to make it predictable for parsers.</p></section></section><section>
+<p>The default format has been changed to standard ISO 8601 (<code>yyyy-MM-dd'T'HH:mm:ss'Z'</code>) to make it predictable for parsers.</p></section></section><section>
<h2><a name="Complete_Release_Notes"></a>Complete Release Notes</h2>
<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></section>
</main>
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 Tue Mar 10 19:55:25 2020
@@ -171,19 +171,19 @@
</li>
<li>
-<p>The handling of the <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-3891">toolchains.xml</a> file has been adjusted with the handling of settings.xml which means it will be searched within the ${maven.home}/conf/ folder and furthermore within the ${user.home}/.m2/ folder.</p>
+<p>The handling of the <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-3891"><code>toolchains.xml</code></a> file has been adjusted with the handling of <code>settings.xml</code> which means it will be searched within the <code>${maven.home}/conf/</code> folder and furthermore within the <code>${user.home}/.m2/</code> folder.</p>
</li>
<li>
-<p>For a better understanding and as an example of the toolchains.xml file has been added to the <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5745">Maven distribution</a>.</p>
+<p>For a better understanding and as an example of the <code>toolchains.xml</code> file has been added to the <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5745">Maven distribution</a>.</p>
</li>
<li>
-<p>Maven has been improved to read the toolchains.xml file <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5754">during initialization</a> instead of waiting till <a class="externalLink" href="http://maven.apache.org/plugins/maven-toolchains-plugin/">maven-toolchains-plugin</a> will read it.</p>
+<p>Maven has been improved to read the <code>toolchains.xml</code> file <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5754">during initialization</a> instead of waiting till <a class="externalLink" href="http://maven.apache.org/plugins/maven-toolchains-plugin/">maven-toolchains-plugin</a> will read it.</p>
</li>
<li>
-<p>Maven has a new option to handle global toolchains file -gt file or --global-toolchains file in the spirit of global settings file<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-3891">MNG-3891</a>.</p>
+<p>Maven has a new option to handle global toolchains file <code>-gt file</code> or <code>--global-toolchains file</code> in the spirit of global settings file<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-3891">MNG-3891</a>.</p>
</li>
</ul></section><section>
<h3><a name="Core_Extensions"></a>Core Extensions</h3>
@@ -195,11 +195,11 @@
</li>
<li>
-<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 it manually into the ${MAVEN_HOME}/lib/ext folder. This means you had to change the Maven installation. The consequence was that everyone 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 mvn -Dmaven.ext.class.path=extension.jar. This has the drawback giving those options to your Maven build every time you are calling Maven. Not very convenient as well.</p>
+<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 it manually into the <code>${MAVEN_HOME}/lib/ext</code> folder. This means you had to change the Maven installation. The consequence was that everyone 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>
</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 ${maven.projectBasedir}/.mvn/extensions.xml 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>${maven.projectBasedir}/.mvn/extensions.xml</code> file which looks like the following:</p>
</li>
</ul>
@@ -216,9 +216,9 @@
<ul>
-<li>Now you can simply use an extension by defining the usual maven coordinates groupId, artifactId, version 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.</li>
+<li>Now you can simply use an extension by defining the usual maven coordinates <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.</li>
</ul>
-<p>An other advantage is that the ${maven.projectBasedir}/.mvn/ 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 can use the extensions.</p>
+<p>An other advantage is that the <code>${maven.projectBasedir}/.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 can use the extensions.</p>
<p>One thing is important that the extensions will be resolved from the pluginRepository. This is important if you have configured the pluginRepository different from the repository.</p></section><section>
<h3><a name="JVM_and_Command_Line_Options"></a>JVM and Command Line Options</h3>
<ul>
@@ -229,15 +229,15 @@
</li>
<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 ${maven.projectBasedir}/.mvn/maven.config file which contains the configuration options for the command line. For example things like -T3 -U --fail-at-end. So you only have to call maven just by using mvn clean package instead of mvn -T3 -U --fail-at-end clean package and not to miss the -T3 -U --fail-at-end options. The ${maven.projectBasedir}/.mvn/maven.config is located in the ${maven.projectBasedir}/.mvn/ folder which is in the root of a multi module build. This folder 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 via mvn -T3 -U --fail-at-end clean package instead of mvn clean package.</p>
+<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 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> folder which is in the root of a multi module build. This folder 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 via <code>mvn -T3 -U --fail-at-e
nd clean package</code> instead of <code>mvn clean package</code>.</p>
</li>
<li>
-<p>In Maven it is not simple to define JVM configuration on a per project base. The existing mechanism based on an environment variable MAVEN_OPTS and the usage of ${user.home}/.mavenrc is an other option with the drawback of not being part of the project.</p>
+<p>In Maven it is not simple to define JVM configuration on a per project base. The existing mechanism based on an environment variable <code>MAVEN_OPTS</code> and the usage of <code>${user.home}/.mavenrc</code> is an other 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 ${maven.projectBasedir}/.mvn/jvm.config 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 MAVEN_OPTS, .mavenrc files. So for example if you put the following JVM options into the ${maven.projectBasedir}/.mvn/jvm.config file</p>
+<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 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>
</ul>
@@ -247,7 +247,7 @@
<ul>
-<li>you don’t need to remember of using this options in MAVEN_OPTS or switching between different configurations.</li>
+<li>you don’t need to remember of using this options in <code>MAVEN_OPTS</code> or switching between different configurations.</li>
</ul></section><section>
<h3><a name="Plugin_Goal_Invocation_from_Command_Line"></a>Plugin Goal Invocation from Command Line</h3>
<ul>
@@ -260,7 +260,7 @@
<div class="source"><pre class="prettyprint linenums">mvn exec:java
</pre></div></div>
-<p>The configuration which is used here can be defined in your pom by using an execution id default-cli.</p>
+<p>The configuration which is used here can be defined in your pom by using an execution id <code>default-cli</code>.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><project...>
@@ -316,7 +316,7 @@
</project>
</pre></div></div>
-<p>So if you like to use the configuration given with the execution id: second-cli this can be done like this:</p>
+<p>So if you like to use the configuration given with the execution id: <code>second-cli</code> this can be done like this:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn exec:java@second-cli
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 Tue Mar 10 19:55:25 2020
@@ -187,7 +187,7 @@
<li>
-<p>The par lifecycle has been removed from the default life cycle bindings and the maven-ejb3-plugin has been removed from default bindings, cause it does not exist <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5892">MNG-5892</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5894">MNG-5894</a>.</p>
+<p>The <code>par</code> lifecycle has been removed from the default life cycle bindings and the maven-ejb3-plugin has been removed from default bindings, cause it does not exist <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5892">MNG-5892</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5894">MNG-5894</a>.</p>
</li>
<li>
@@ -247,7 +247,7 @@
</li>
<li>
-<p>Upgrade <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-utils/">plexus-utils</a> to 3.0.22 to support combine.id as configuration attribute for Map merging <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5922">MNG-5922</a>.</p>
+<p>Upgrade <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-utils/">plexus-utils</a> to 3.0.22 to support <code>combine.id</code> as configuration attribute for Map merging <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5922">MNG-5922</a>.</p>
</li>
<li>
@@ -263,15 +263,15 @@
</li>
<li>
-<p>The Cygwin Shell related handling of the MAVEN_PROJECTBASEDIR has been fixed with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5812">MNG-5812</a>.</p>
+<p>The Cygwin Shell related handling of the <code>MAVEN_PROJECTBASEDIR</code> has been fixed with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5812">MNG-5812</a>.</p>
</li>
<li>
-<p>The scripts to call Maven has introduced a bug related to the handling of the MAVEN_OPTS and debugging options which has been fixed by <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5813">MNG-5813</a>.</p>
+<p>The scripts to call Maven has introduced a bug related to the handling of the <code>MAVEN_OPTS</code> and debugging options which has been fixed by <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5813">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 ${maven.projectBasedir}/.mvn folder of the project. There you can use the maven.config 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 class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5816">MNG-5816</a>.</p>
+<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> folder 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 class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5816">MNG-5816</a>.</p>
</li>
<li>
@@ -283,11 +283,11 @@
</li>
<li>
-<p>The <prerequisites> elements is intended for <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-4840">buildtime checking but not for runtime checks</a> which should be left to <a href="/enforcer/maven-enforcer-plugin/">maven-enforcer-plugin</a>. This has not been documented accordingly. This has been done with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5297">MNG-5297</a>.</p>
+<p>The <code><prerequisites></code> elements is intended for <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-4840">buildtime checking but not for runtime checks</a> which should be left to <a href="/enforcer/maven-enforcer-plugin/">maven-enforcer-plugin</a>. This has not been documented accordingly. This has been done with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5297">MNG-5297</a>.</p>
</li>
<li>
-<p>In situations like this: mvn -Dtest=\"anton\" clean package the trailing quote is stripped away which could cause problems. This has been fixed with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5681">MNG-5681</a>.</p>
+<p>In situations like this: <code>mvn -Dtest=\"anton\" clean package</code> the trailing quote is stripped away which could cause problems. This has been fixed with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5681">MNG-5681</a>.</p>
</li>
<li>
@@ -295,7 +295,7 @@
</li>
<li>
-<p>There had been several issues with the mvn script which are for example wrong locating the .mvn folder, nonportable shell constructs, wrongly setting ‘maven.multiModuleProjectDirectory’ variable or directories which contain spaces. Those issues have been fixed <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5786">MNG-5786</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5858">MNG-5858</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5882">MNG-5882</a> and <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5884">MNG-5884</a>.</p>
+<p>There had been several issues with the <code>mvn</code> script which are for example wrong locating the <code>.mvn</code> folder, nonportable shell constructs, wrongly setting ‘maven.multiModuleProjectDirectory’ variable or directories which contain spaces. Those issues have been fixed <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5786">MNG-5786</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5858">MNG-5858</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5882">MNG-5882</a> and <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5884">MNG-5884</a>.</p>
</li>
<li>
Modified: maven/website/content/docs/3.5.0-alpha-1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.5.0-alpha-1/release-notes.html (original)
+++ maven/website/content/docs/3.5.0-alpha-1/release-notes.html Tue Mar 10 19:55:25 2020
@@ -167,8 +167,8 @@
<p>The following issues were identified during release testing of this <i>ALPHA</i> release but have not been deemed as release blockers:</p>
<ul>
-<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6177">MNG-6177</a> The --file and -f option to specify a pom.xml to use does not work if the path includes characters that need quoting such as whitespace or &.</li>
-<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6115">MNG-6115</a> If Maven is installed in a writable location, every build will create a new lib/ext/jansi-.... file.</li>
+<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6177">MNG-6177</a> The <code>--file</code> and <code>-f</code> option to specify a <code>pom.xml</code> to use does not work if the path includes characters that need quoting such as whitespace or <code>&</code>.</li>
+<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6115">MNG-6115</a> If Maven is installed in a writable location, every build will create a new <code>lib/ext/jansi-....</code> file.</li>
</ul></section><section>
<h2><a name="Why_not_Maven_3.4.0.3F"></a>Why not Maven 3.4.0?</h2>
<p>After Maven 3.3.9 was released, the Eclipse Aether project was retired and the code base was migrated to the Apache Maven project.</p>
@@ -210,11 +210,11 @@
</li>
<li>
-<p>The new project.directory special property adds support in every calculated URLs (project, SCM, site) for module directory name that does not match artifactId <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5878">MNG-5878</a></p>
+<p>The new <code>project.directory</code> special property adds support in every calculated URLs (project, SCM, site) for module directory name that does not match artifactId <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5878">MNG-5878</a></p>
</li>
<li>
-<p>The JAVA_HOME discovery has been reduced to simply check if JAVA_HOME is set or not then trying to discover via which java, nothing more <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6003">MNG-6003</a>.</p>
+<p>The <code>JAVA_HOME</code> discovery has been reduced to simply check if <code>JAVA_HOME</code> is set or not then trying to discover via <code>which java</code>, nothing more <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6003">MNG-6003</a>.</p>
</li>
<li>
@@ -222,19 +222,19 @@
</li>
<li>
-<p>Based on problems in using M2_HOME related to different Maven versions installed and to simplify things, the usage of M2_HOME has been removed and is not supported any more <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5823">MNG-5823</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5836">MNG-5836</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5607">MNG-5607</a>.</p>
+<p>Based on problems in using <code>M2_HOME</code> related to different Maven versions installed and to simplify things, the usage of <code>M2_HOME</code> has been removed and is not supported any more <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5823">MNG-5823</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5836">MNG-5836</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5607">MNG-5607</a>.</p>
</li>
<li>
-<p>Important change for windows users: The usage of %HOME% has been replaced with %USERPROFILE% <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6001">MNG-6001</a></p>
+<p>Important change for windows users: The usage of <code>%HOME%</code> has been replaced with <code>%USERPROFILE%</code> <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6001">MNG-6001</a></p>
</li>
<li>
-<p>Several issues have been reported and fixed related to the mvn script either for Unix/Linux/Cygwin/Solaris or for Windows <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5815">MNG-5815</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5852">MNG-5852</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5963">MNG-5963</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6022">MNG-6022</a>.</p>
+<p>Several issues have been reported and fixed related to the <code>mvn</code> script either for Unix/Linux/Cygwin/Solaris or for Windows <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5815">MNG-5815</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5852">MNG-5852</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5963">MNG-5963</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6022">MNG-6022</a>.</p>
</li>
<li>
-<p>In Maven 3.3.9, we have removed bindings for maven-ejb3-plugin because it does not exist. We follow-up and removed the artifact handler for ejb3 and the par lifecycle <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6014">MNG-6014</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6017">MNG-6017</a>.</p>
+<p>In Maven 3.3.9, we have removed bindings for maven-ejb3-plugin because it does not exist. We follow-up and removed the artifact handler for <code>ejb3</code> and the <code>par</code> lifecycle <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6014">MNG-6014</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6017">MNG-6017</a>.</p>
</li>
<li>
@@ -242,11 +242,11 @@
</li>
<li>
-<p>If you have defined a property within the .mvn/maven.config file, it was not possible to overwrite the property via command line. This has been fixed with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6078">MNG-6078</a>.</p>
+<p>If you have defined a property within the <code>.mvn/maven.config</code> file, it was not possible to overwrite the property via command line. This has been fixed with <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6078">MNG-6078</a>.</p>
</li>
<li>
-<p>If you have are using <prerequisites>..</prerequisites> for a non maven-plugin project, you will get a WARNING which looks like this:</p>
+<p>If you have are using <code><prerequisites>..</prerequisites></code> for a non maven-plugin project, you will get a WARNING which looks like this:</p>
</li>
</ul>
@@ -255,7 +255,7 @@
[WARNING] The project org.apache.maven:maven:pom:3.5.0-SNAPSHOT uses prerequisites which is only intended for maven-plugin projects but not for non maven-plugin projects. For such purposes you should use the maven-enforcer-plugin. See https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
</pre></div></div>
-<p>This will tell you to use maven-enforcer-plugin to check the version of Maven you are expecting to build your project with, instead of using prerequisites <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5297">MNG-5297</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6092">MNG-6092</a>.</p>
+<p>This will tell you to use maven-enforcer-plugin to check the version of Maven you are expecting to build your project with, instead of using <code>prerequisites</code> <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-5297">MNG-5297</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6092">MNG-6092</a>.</p>
<ul>
<li>Replaced Eclipse Aether with <a href="/resolver/">Maven Resolver</a> <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6110">MNG-6110</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6140">MNG-6140</a>.</li>