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 2023/02/18 18:17:31 UTC
svn commit: r1907741 [1/3] - in /maven/website/content: ./ archives/maven-2.x/ developers/ developers/conventions/ docs/3.2.2/ docs/3.3.1/ docs/3.5.0-alpha-1/ docs/3.5.0/ docs/3.6.0/ docs/3.6.1/ examples/ guides/development/ guides/getting-started/ gui...
Author: svn-site-role
Date: Sat Feb 18 18:17:30 2023
New Revision: 1907741
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/aether.html
maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html
maven/website/content/configure.html
maven/website/content/developers/committer-settings.html
maven/website/content/developers/conventions/code.html
maven/website/content/developers/conventions/git.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.5.0-alpha-1/release-notes.html
maven/website/content/docs/3.5.0/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/examples/injecting-properties-via-settings.html
maven/website/content/faq-unoffical.html
maven/website/content/guides/development/guide-documentation-style.html
maven/website/content/guides/development/guide-maven-development.html
maven/website/content/guides/development/guide-plugin-documentation.html
maven/website/content/guides/development/guide-testing-development-plugins.html
maven/website/content/guides/development/guide-testing-releases.html
maven/website/content/guides/getting-started/index.html
maven/website/content/guides/getting-started/maven-in-five-minutes.html
maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html
maven/website/content/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
maven/website/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
maven/website/content/guides/introduction/introduction-to-profiles.html
maven/website/content/guides/introduction/introduction-to-repositories.html
maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
maven/website/content/guides/introduction/introduction-to-the-pom.html
maven/website/content/guides/mini/guide-archive-configuration.html
maven/website/content/guides/mini/guide-assemblies.html
maven/website/content/guides/mini/guide-attached-tests.html
maven/website/content/guides/mini/guide-building-for-different-environments.html
maven/website/content/guides/mini/guide-configuring-maven.html
maven/website/content/guides/mini/guide-configuring-plugins.html
maven/website/content/guides/mini/guide-creating-archetypes.html
maven/website/content/guides/mini/guide-default-execution-ids.html
maven/website/content/guides/mini/guide-deployment-security-settings.html
maven/website/content/guides/mini/guide-encryption.html
maven/website/content/guides/mini/guide-generating-sources.html
maven/website/content/guides/mini/guide-http-settings.html
maven/website/content/guides/mini/guide-large-scale-centralized-deployments.html
maven/website/content/guides/mini/guide-maven-classloading.html
maven/website/content/guides/mini/guide-mirror-settings.html
maven/website/content/guides/mini/guide-multiple-repositories.html
maven/website/content/guides/mini/guide-proxies.html
maven/website/content/guides/mini/guide-releasing.html
maven/website/content/guides/mini/guide-relocation.html
maven/website/content/guides/mini/guide-repository-ssl.html
maven/website/content/guides/mini/guide-reproducible-builds.html
maven/website/content/guides/mini/guide-site.html
maven/website/content/guides/mini/guide-snippet-macro.html
maven/website/content/guides/mini/guide-using-ant.html
maven/website/content/guides/mini/guide-using-extensions.html
maven/website/content/guides/mini/guide-wagon-providers.html
maven/website/content/guides/plugin/guide-java-plugin-development.html
maven/website/content/guides/plugin/guide-java-report-plugin-development.html
maven/website/content/maven-site-1.0-site.jar
maven/website/content/plugin-developers/common-bugs.html
maven/website/content/plugin-developers/cookbook/plexus-plugin-upgrade.html
maven/website/content/plugin-developers/plugin-testing.html
maven/website/content/plugins/localization.html
maven/website/content/repository/central-index.html
maven/website/content/repository/guide-central-repository-upload.html
maven/website/content/security-plexus-archiver.html
maven/website/content/skins/index.html
Modified: maven/website/content/aether.html
==============================================================================
--- maven/website/content/aether.html (original)
+++ maven/website/content/aether.html Sat Feb 18 18:17:30 2023
@@ -177,8 +177,8 @@ and through <a href="https://issues.apac
<td>no OSGi bundles in Apache Maven</td></tr>
<tr class="b">
<td><strong>P2 repo</strong></td>
-<td><a href="http://download.eclipse.org/aether/aether-core/releases/" class="externalLink">http://download.eclipse.org/aether/aether-core/releases/</a><br /><a href="http://download.eclipse.org/aether/maven-aether-provider/releases/" class="externalLink">http://download.eclipse.org/aether/maven-aether-provider/releases/</a></td>
-<td>no P2 repo</td></tr>
+<td><<a href="http://download.eclipse.org/aether/aether-core/releases/" class="externalLink">http://download.eclipse.org/aether/aether-core/releases/</a><br /><a href="http://download.eclipse.org/aether/maven-aether-provider/releases/" class="externalLink">http://download.eclipse.org/aether/maven-aether-provider/releases/</a></td>
+<td>no> P2 repo</td></tr>
<tr class="a">
<td><strong>API java packages</strong></td>
<td>org.eclipse.aether…</td>
Modified: maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html
==============================================================================
--- maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html (original)
+++ maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html Sat Feb 18 18:17:30 2023
@@ -243,7 +243,7 @@ jason: so when you and benjamin went thr
[08:15am] bentmann: Not sure what kind of consistency you actually require
[08:16am] bentmann: The IT profile should be named equal for all of them
[08:16am] bentmann: by inheriting from the parent
-[08:16am] i386_ left the chat room. (i386_)
+[08:16am] i386_left the chat room. (i386_)
[08:16am] bentmann: whether the are run by Invoker or Shitty shouldn't matter, I guess
[08:17am] jason: no, the actual project just needs a profile name the same. not taken from the parent but stated in the project itself
[08:17am] jason: though the parent could specify that profile which just echos “No ITs”
@@ -281,8 +281,8 @@ the standard Maven components. Here's th
<p>{code}
main is org.apache.maven.cli.MavenCli from plexus.core</p>
<p>set maven.home default ${user.home}/m2</p>
-<p>[plexus.core]<br />
-load ${maven.home}/tycho/<em>.jar<br />
+<p>[plexus.core]
+load ${maven.home}/tycho/<em>.jar
load ${maven.home}/lib/</em>.jar
{code}</p>
<ul>
@@ -311,11 +311,11 @@ behavior, Oleg and I decided to make a b
<p>Find the best people in the world to help create an awesome HTTP and DAV implementation. We did this by talking to Greg, Jan, and Jesse who are the Jetty folks
and there just isn't anyone who knows HTTP better. Greg and Jan are awesome, and Jesse is Maven committer so we have some deep understanding of the issues involved. So
what Oleg and I wanted to see was:
-** Easy SSL support where mucky with certificates in the default install is not required.
+**Easy SSL support where mucky with certificates in the default install is not required.
** Connection pooling
-** Connection parallelization
+**Connection parallelization
** Built in DAV client support for deployment
-** Atomic retrieval: we make sure absolutely everything is been safely transported to disk before we place it in the local Maven repository
+**Atomic retrieval: we make sure absolutely everything is been safely transported to disk before we place it in the local Maven repository
** Atomic deployment: in this case we could only support this using a special filter Greg created which blocks requests for any artifacts being deploy in the current
set until the entire set land safely to disk. So it becomes impossible to ask for an artifact that refers to something else in the set before it is actually available.
** Starting thinking about a client that can understand GeoIP. Given the recent spikes in traffic we are going to start needing to distribute the load.</p></li>
@@ -346,12 +346,12 @@ as he's seen Maven in action in one of t
<li>
<p>Project Builder ([architecture|http://docs.codehaus.org/display/MAVENUSER/Project+Builder])
-** Maven shared model work: a new way of reading in the models for Maven that is not format dependent in any way i.e. XML, text, YAML, scripts, whatever.
+**Maven shared model work: a new way of reading in the models for Maven that is not format dependent in any way i.e. XML, text, YAML, scripts, whatever.
** Pluggable model readers: this could leverage different implementations provided by the shared model work, but we still need a way to detect the type and version
of the model that we want to consume
-** A new terse format that uses attributes
+**A new terse format that uses attributes
** Automatic parent versioning
-** New interpolation component (plexus-interpolation)
+**New interpolation component (plexus-interpolation)
** Dynamic build sections ([MNG-3530|http://jira.codehaus.org/browse/MNG-3530])
** Mixin support – allowing a paramterizable template which can be imported with one line.</p></li>
<li>
@@ -369,7 +369,7 @@ clients that want to separate the tools
<p>Domain logging</p></li>
<li>
<p>Plugin Manager
-** Removal of the Plugin Registry (done) – we moved in a direction where people lock down their versions and we've helped by putting default versions
+**Removal of the Plugin Registry (done) – we moved in a direction where people lock down their versions and we've helped by putting default versions
in the parent POM.
** Load Plugin dependencies into a separate ClassRealm (done)
** Plugin Execution Environment: Ability to run any version of a plugin where an environment is created which contains all the
@@ -413,9 +413,9 @@ source level gleaning again. Jason Dillo
<ul>
<li>Extensions
-** Different categories of extensions: providers vs packaging vs PMD/Checkstyle resources stuff in a JAR
+**Different categories of extensions: providers vs packaging vs PMD/Checkstyle resources stuff in a JAR
** Transparent Extension Loading
-*** Any Wagon or SCM providers should get picked up automatically from SCM and distributionManagement URLs
+***Any Wagon or SCM providers should get picked up automatically from SCM and distributionManagement URLs
*** Any extensions containing packaging/lifecycle related bits needs to be picked up automatically</li>
</ul>
</main>
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Sat Feb 18 18:17:30 2023
@@ -150,22 +150,22 @@ under the License.
<p>The configuration for Apache Maven usage itself and projects built with resides
in a number of places:</p><section>
-<h2><code>MAVEN_OPTS</code> environment variable:</h2>
+<h2><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 it. E.g. JVM memory
settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
-<h2><code>MAVEN_ARGS</code> environment variable:</h2>
+<h2><code>MAVEN_ARGS</code> environment variable</h2>
<p>Starting with Maven 3.9.0, this variable contains arguments passed to Maven before
CLI arguments. E.g., options and goals could be defined with the value
<code>-B -V checkstyle:checkstyle</code>.</p></section><section>
-<h2><code>settings.xml</code> file:</h2>
+<h2><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><code>.mvn</code> directory:</h2>
+<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>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>
+<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
it manually into the <code>${MAVEN_HOME}/lib/ext</code> directory. 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
@@ -183,7 +183,7 @@ options to your Maven build every time y
</extensions>
</code></pre></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><code>.mvn/maven.config</code> file:</h3>
+<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
@@ -196,7 +196,7 @@ The <code>${maven.projectBasedir}/.mvn/m
-U
--fail-at-end
</code></pre></div></section><section>
-<h3><code>.mvn/jvm.config</code> file:</h3>
+<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>
<div class="source"><pre class="prettyprint linenums"><code>-Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
Modified: maven/website/content/developers/committer-settings.html
==============================================================================
--- maven/website/content/developers/committer-settings.html (original)
+++ maven/website/content/developers/committer-settings.html Sat Feb 18 18:17:30 2023
@@ -165,7 +165,7 @@ under the License.
<p>Maven uses several servers configuration to deploy snapshots and releases on the Apache servers. You need to tell to Maven what your Apache username is.</p>
<p><strong>It is highly recommended to use Maven's <a href="../guides/mini/guide-encryption.html">password encryption capabilities</a> for your passwords</strong>.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><settings>
...
<servers>
<!-- To publish a snapshot of some part of Maven -->
@@ -187,7 +187,7 @@ under the License.
<h3>Enable sending announcement e-mails</h3>
<p>To be able to send out announcements of Maven releases you need to add a couple of properties to the <code>apache-release</code> profile.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><settings>
...
<profiles>
<profile>
Modified: maven/website/content/developers/conventions/code.html
==============================================================================
--- maven/website/content/developers/conventions/code.html (original)
+++ maven/website/content/developers/conventions/code.html Sat Feb 18 18:17:30 2023
@@ -249,7 +249,7 @@ under the License.
<p><strong>Line Breaks</strong>: Always use a new line with indentation for complex XML types and no line break for simple XML types. Always use a new line to separate XML sections or blocks, for instance:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><aTag>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><aTag>
<simpleType>This is a simple type</simpleType>
<complexType>
@@ -259,11 +259,11 @@ under the License.
</code></pre></div>
<p>In some cases, adding comments could improve the readability of blocks, for instance:</p>
-<div class="source"><pre class="prettyprint linenums"><code> <!-- Simple XML documentation -->
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> <!-- Simple XML documentation -->
</code></pre></div>
<p>or</p>
-<div class="source"><pre class="prettyprint linenums"><code> <!-- ====================================================================== -->
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> <!-- ====================================================================== -->
<!-- Block documentation -->
<!-- ====================================================================== -->
</code></pre></div></section><section>
@@ -273,7 +273,7 @@ under the License.
<p>The team has <a href="https://lists.apache.org/thread/h8px5t6f3q59cnkzpj1t02wsoynr3ygk" class="externalLink">voted</a> during the end of June 2008 to follow a specific POM convention to ordering POM elements. The consequence of this vote is that the <a href="https://maven.apache.org/ref/current/maven-model/maven.html" class="externalLink">Maven project descriptor</a> is <strong>no more</strong> considered as the reference for the ordering.</p>
<p>The following is the recommended ordering for all Maven POM files:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion/>
<parent/>
Modified: maven/website/content/developers/conventions/git.html
==============================================================================
--- maven/website/content/developers/conventions/git.html (original)
+++ maven/website/content/developers/conventions/git.html Sat Feb 18 18:17:30 2023
@@ -201,12 +201,12 @@ o Applied without change
<h3>Edit Commit Message</h3>
<p>to edit last commit comment:</p>
-<div class="source"><pre class="prettyprint linenums"><code>$ git commit --amend -m "new comment"
+<div class="source"><pre class="prettyprint linenums"><code>git commit --amend -m "new comment"
</code></pre></div></section><section>
<h3>Workflow</h3>
<p>Workflow for svn folks is something like :</p>
-<div class="source"><pre class="prettyprint linenums"><code> $ git pull
+<div class="source"><pre class="prettyprint linenums"><code class="language-bash"> $ git pull
$ hack hack hack
$ git push
// fails, because someone else has already pushed to master
@@ -216,7 +216,7 @@ o Applied without change
</code></pre></div>
<p>A more quiet workflow :</p>
-<div class="source"><pre class="prettyprint linenums"><code>$ git pull
+<div class="source"><pre class="prettyprint linenums"><code class="language-bash">$ git pull
$ hack hack hack
$ git push
// fails, because someone else has already pushed to master
@@ -229,7 +229,7 @@ $ git push
<h3>Other useful Git commands while developing</h3>
<p>If you've done a chunk of work and you would like to ditch your changes and start from scratch use this command to revert to the original checkout:</p>
-<div class="source"><pre class="prettyprint linenums"><code>$ git checkout .
+<div class="source"><pre class="prettyprint linenums"><code>git checkout .
</code></pre></div>
<p>TODO .gitignore</p><section>
<h4>power-git checkout</h4>
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 Sat Feb 18 18:17:30 2023
@@ -161,7 +161,7 @@ See the <a href="../../plugins/index.htm
<h3>Support version ranges in parent elements (<a href="https://issues.apache.org/jira/browse/MNG-2199" class="externalLink">MNG-2199</a>)</h3>
<p>Parent elements can now use bounded ranges in the version specification. You can now consistently use ranges for all intra-project dependencies, of which parents are a special case but still considered a dependency of projects that inherit from them. The following is now permissible:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -183,7 +183,7 @@ See the <a href="../../plugins/index.htm
<h3>Update maven-plugin-plugin:descriptor default binding from generate-resources phase to process-classes (<a href="https://issues.apache.org/jira/browse/MNG-5346" class="externalLink">MNG-5346</a>)</h3>
<p>Now when you use create plugins that strictly use annotation processing to generate the descriptor, you can avoid the confusing configuration previously required. This is what you typically needed to include in order to run the descriptor generator on compiled classes and avoid errors.</p>
-<div class="source"><pre class="prettyprint linenums"><code> <pluginManagement>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> <pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
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 Sat Feb 18 18:17:30 2023
@@ -281,7 +281,7 @@ between different configurations.</li>
</code></pre></div>
<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"><pre class="prettyprint linenums"><code><project...>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project...>
<build>
<plugins>
@@ -305,7 +305,7 @@ between different configurations.</li>
<p>Starting with this Maven release you can now define several configuration for different
executions on command like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project...>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project...>
<build>
<plugins>
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 Sat Feb 18 18:17:30 2023
@@ -149,7 +149,7 @@
<p>This is an <i>ALPHA</i> release. There is the potential that features may be added/removed between this release and the first GA release in the 3.5.x release line.</p>
-<p><i>Please consult the Known Issues section below before use</i></p>
+<p><i>Please consult the Known Issues section below before use</i></p>
</div>
<p>Maven 3.5.0-alpha-1 is <a href="../../download.html">available for download</a>.</p>
Modified: maven/website/content/docs/3.5.0/release-notes.html
==============================================================================
--- maven/website/content/docs/3.5.0/release-notes.html (original)
+++ maven/website/content/docs/3.5.0/release-notes.html Sat Feb 18 18:17:30 2023
@@ -253,7 +253,7 @@
<li><a href="https://issues.apache.org/jira/browse/MNG-5962" class="externalLink">MNG-5962</a> - <code>mvn.cmd</code> fails when the current directory has spaces in between</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5963" class="externalLink">MNG-5963</a> - <code>mvn.cmd</code> does not return ERROR_CODE</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6022" class="externalLink">MNG-6022</a> - <code>mvn.cmd</code> fails if directory contains an ampersand (<code>&</code>)</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6053" class="externalLink">MNG-6053</a> - Unsafe System Properties copy in <code>MavenRepositorySystemUtils</code>, causing NPEs</li>
+<li>[MNG-6053][] - Unsafe System Properties copy in <code>MavenRepositorySystemUtils</code>, causing NPEs</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a> - Problem with CI friendly usage of `${..} reactor order is changed</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6090" class="externalLink">MNG-6090</a> - CI friendly properties break submodule builds</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6105" class="externalLink">MNG-6105</a> - <code>properties.internal.SystemProperties.addSystemProperties()</code> is not really thread-safe</li>
@@ -312,12 +312,12 @@
<li><a href="https://issues.apache.org/jira/browse/MNG-6145" class="externalLink">MNG-6145</a> - Remove non-existent m2 include in <code>component.xml</code></li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6146" class="externalLink">MNG-6146</a> - Several small stylistic and spelling improvements to code and documentation</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6147" class="externalLink">MNG-6147</a> - `MetadataResolutionResult#getGraph()`` contains duplicate if clause</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6150" class="externalLink">MNG-6150</a> - Javadoc improvements for 3.5.0</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6163" class="externalLink">MNG-6163</a> - Introduce <code>CLASSWORLDS_JAR</code> in shell startup scripts</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6165" class="externalLink">MNG-6165</a> - Deprecate and replace incorrectly spelled public API</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6179" class="externalLink">MNG-6179</a> - Remove unused prerequisites</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6185" class="externalLink">MNG-6185</a> - Replace doclettag explanation with annotations in AbstractMojo javadoc</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6189" class="externalLink">MNG-6189</a> - WARN if maven-site-plugin configuration contains <code>reportPlugins</code> element</li>
+<li>[MNG-6150][] - Javadoc improvements for 3.5.0</li>
+<li>[MNG-6163][] - Introduce <code>CLASSWORLDS_JAR</code> in shell startup scripts</li>
+<li>[MNG-6165][] - Deprecate and replace incorrectly spelled public API</li>
+<li>[MNG-6179][] - Remove unused prerequisites</li>
+<li>[MNG-6185][] - Replace doclettag explanation with annotations in AbstractMojo javadoc</li>
+<li>[MNG-6189][] - WARN if maven-site-plugin configuration contains <code>reportPlugins</code> element</li>
</ul></section><section>
<h3>New Features</h3>
<ul>
@@ -325,25 +325,25 @@
<li><a href="https://issues.apache.org/jira/browse/MNG-3507" class="externalLink">MNG-3507</a> - ANSI color logging for improved output visibility</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5878" class="externalLink">MNG-5878</a> - add support for module name != <code>artifactId</code> in every calculated URLs (project, SCM, site): special <code>project.directory</code> property</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6093" class="externalLink">MNG-6093</a> - create a <code>slf4j-simple</code> provider extension that supports level color rendering</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6182" class="externalLink">MNG-6182</a> - ModelResolver interface enhancement: addition of <code>resolveModel(Dependency)</code> supporting version ranges</li>
+<li>[MNG-6182][] - ModelResolver interface enhancement: addition of <code>resolveModel(Dependency)</code> supporting version ranges</li>
</ul></section><section>
<h3>Tasks</h3>
<ul>
-<li><a href="https://issues.apache.org/jira/browse/MNG-5954" class="externalLink">MNG-5954</a> - Remove outdated <code>maven-embedder/src/main/resources/META-INF/MANIFEST.MF</code></li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6106" class="externalLink">MNG-6106</a> - Remove <code>maven.home</code> default value setter from <code>m2.conf</code></li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6136" class="externalLink">MNG-6136</a> - Upgrade Maven Wagon from 2.10 to 2.12</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6137" class="externalLink">MNG-6137</a> - Clean up duplicate dependencies caused by incomplete Wagon HTTP Provider exclusions</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6138" class="externalLink">MNG-6138</a> - Remove obsolete <code>message_*.properties</code> from maven-core</li>
+<li>[MNG-5954][] - Remove outdated <code>maven-embedder/src/main/resources/META-INF/MANIFEST.MF</code></li>
+<li>[MNG-6106][] - Remove <code>maven.home</code> default value setter from <code>m2.conf</code></li>
+<li>[MNG-6136][] - Upgrade Maven Wagon from 2.10 to 2.12</li>
+<li>[MNG-6137][] - Clean up duplicate dependencies caused by incomplete Wagon HTTP Provider exclusions</li>
+<li>[MNG-6138][] - Remove obsolete <code>message_*.properties</code> from maven-core</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6140" class="externalLink">MNG-6140</a> - update documentation's dependency graph with <code>resolver</code> + <code>resolver-provider</code> + <code>slf4j-provider</code></li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6151" class="externalLink">MNG-6151</a> - Force Push master from <code>737de43e392fc15a0ce366db98d70aa18b3f6c03</code></li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6152" class="externalLink">MNG-6152</a> - Add a <code>Jenkinsfile</code> so that builds.apache.org can use multibranch pipeline</li>
+<li>[MNG-6151][] - Force Push master from <code>737de43e392fc15a0ce366db98d70aa18b3f6c03</code></li>
+<li>[MNG-6152][] - Add a <code>Jenkinsfile</code> so that builds.apache.org can use multibranch pipeline</li>
</ul></section><section>
<h3>Wishes</h3>
<ul>
-<li><a href="https://issues.apache.org/jira/browse/MNG-2199" class="externalLink">MNG-2199</a> - Support version ranges in parent elements</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6088" class="externalLink">MNG-6088</a> - after forked execution success, add an empty line</li>
+<li>[MNG-2199][] - Support version ranges in parent elements</li>
+<li>[MNG-6088][] - after forked execution success, add an empty line</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6092" class="externalLink">MNG-6092</a> - warn if <code>prerequisites.maven</code> is used for non-plugin projects</li>
</ul></section></section><section>
<h2>Complete Release Notes</h2>
Modified: maven/website/content/docs/3.6.0/release-notes.html
==============================================================================
--- maven/website/content/docs/3.6.0/release-notes.html (original)
+++ maven/website/content/docs/3.6.0/release-notes.html Sat Feb 18 18:17:30 2023
@@ -249,7 +249,7 @@ versions each line will contain the appr
can cause issues which has been fixed.</li>
</ul></section><section>
<h2><a href="#details">The detailed issue list</a></h2><section>
-<h3>Bugs:</h3>
+<h3>Bugs</h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/MNG-6311" class="externalLink">MNG-6311</a> - Maven intolerably slow when import scope used heavily in large project</li>
@@ -260,7 +260,7 @@ can cause issues which has been fixed.</
<li><a href="https://issues.apache.org/jira/browse/MNG-6472" class="externalLink">MNG-6472</a> - Mockito cannot mock this class: interface org.eclipse.aether.impl.RepositoryEventDispatcher</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6490" class="externalLink">MNG-6490</a> - Maven shall not fail reporting circular dependency when the dependency is a classified secondary artifact</li>
</ul></section><section>
-<h3>Improvements:</h3>
+<h3>Improvements</h3>
<ul>
<li><a href="https://issues.apache.org/jira/browse/MNG-4508" class="externalLink">MNG-4508</a> - No way to avoid adding artifactId to site urls</li>
Modified: maven/website/content/docs/3.6.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.6.1/release-notes.html (original)
+++ maven/website/content/docs/3.6.1/release-notes.html Sat Feb 18 18:17:30 2023
@@ -282,7 +282,7 @@ URL's etc. within <code>project</code>,
builds like this:</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project child.project.url.inherit.append.path="false">
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project child.project.url.inherit.append.path="false">
<url>...</url>
<scm child.scm.connection.inherit.append.path="false"
@@ -302,7 +302,7 @@ builds like this:</li>
</code></pre></div>
<p>Detailed explanations can be found in <a href="https://maven.apache.org/ref/3.6.1/maven-model-builder/index.html#Inheritance_Assembly" class="externalLink">Inheritance Assembly</a> and in <a href="http://issues.apache.org/jira/browse/MNG-6059" class="externalLink">MNG-6059</a></p></section><section>
<h2>The detailed issue list<a href="#details"></a></h2><section>
-<h3>Bugs:</h3>
+<h3>Bugs</h3>
<ul>
<li><a href="http://issues.apache.org/jira/browse/MNG-5705" class="externalLink">MNG-5705</a> - NPE on parallel build in BuilderCommon.handleBuildError(BuilderCommon.java:147)</li>
Modified: maven/website/content/examples/injecting-properties-via-settings.html
==============================================================================
--- maven/website/content/examples/injecting-properties-via-settings.html (original)
+++ maven/website/content/examples/injecting-properties-via-settings.html Sat Feb 18 18:17:30 2023
@@ -147,7 +147,7 @@ under the License.
<p>You have a plugin parameter that should contain a user-specific value. This parameter has a common format (relative directory structure), but depends on knowing the directory of the installed application or something.</p></section><section>
<h3>Plugin Configuration</h3>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<build>
<plugins>
@@ -164,7 +164,7 @@ under the License.
</code></pre></div></section><section>
<h3><code>settings.xml</code></h3>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><settings>
[...]
<profiles>
<profile>
Modified: maven/website/content/faq-unoffical.html
==============================================================================
--- maven/website/content/faq-unoffical.html (original)
+++ maven/website/content/faq-unoffical.html Sat Feb 18 18:17:30 2023
@@ -521,7 +521,7 @@ plugins will be available soon, currentl
<p><a href="http://maven.apache.org/guides/mini/guide-mirror-settings.html" class="externalLink">Guide mirror settings</a></p>
<p><em>Repositories, General</em></p></section><section>
<h3>How do I get a list of archetypes?</h3>
-<p>To get a list of archetypes, refer to the following page [<a href="http://svn.apache.org/viewcvs.cgi/maven/archetype/trunk/maven-archetypes" class="externalLink">http://svn.apache.org/viewcvs.cgi/maven/archetype/trunk/maven-archetypes</a>)</p></section><section>
+<p>To get a list of archetypes, refer to the following page [<a href="http://svn.apache.org/viewcvs.cgi/maven/archetype/trunk/maven-archetypes)" class="externalLink">http://svn.apache.org/viewcvs.cgi/maven/archetype/trunk/maven-archetypes)</a></p></section><section>
<h3>How do I specify my remote repo in Maven?</h3>
<p>To specify a remote repo in Maven, add the <code><repositories></code> element to the POM:</p>
@@ -533,7 +533,7 @@ plugins will be available soon, currentl
</repository>
</repositories>
</code></pre></div>
-<p>Or, refer to the following page [<a href="http://maven.apache.org/guides/mini/guide-multiple-repositories.html" class="externalLink">http://maven.apache.org/guides/mini/guide-multiple-repositories.html</a>)
+<p>Or, refer to the following page [<a href="http://maven.apache.org/guides/mini/guide-multiple-repositories.html)" class="externalLink">http://maven.apache.org/guides/mini/guide-multiple-repositories.html)</a>
<em>Repositories</em></p></section><section>
<h3>How do I specify which output directories the Eclipse plugin puts into the .classpath file?</h3>
@@ -655,7 +655,7 @@ plugins will be available soon, currentl
<p> <em>Sites & Reporting</em></p></section><section>
<h3>How do I specify that all web modules will inherit the group's common files from a parent web module?</h3>
<p>maven-war-plugin 2.0-beta-3 and later supports merging of wars. Just reference the common WAR project from another WAR project as a dependency of <code><type>war</type></code> and it will automatically be merged.</p>
-<p>See [<a href="http://jira.codehaus.org/browse/MWAR-8" class="externalLink">http://jira.codehaus.org/browse/MWAR-8</a>)</p>
+<p>See [<a href="http://jira.codehaus.org/browse/MWAR-8)" class="externalLink">http://jira.codehaus.org/browse/MWAR-8)</a></p>
<p><em>Inheritence and Interpolation</em></p></section><section>
<h3>How do I determine which POM contains missing transitive dependency?</h3>
<p>run <code>mvn -X</code></p>
@@ -1131,7 +1131,7 @@ specified, and allowing the use of artif
<p>Absolutely yes!</p>
<p>By configuring <code><sourceDirectory></code>, <code><resources></code> and other elements of the <code><build></code> section.</p>
<p>In addition, you may need to change the plugin configuration if you are not using plugin defaults for their files/directories.</p></section><section>
-<h3>Where is the source code? I couldn't seem to find a link anywhere on the Maven site.</h3>
+<h3>Where is the source code? I couldn't seem to find a link anywhere on the Maven site</h3>
<p>The source code can be found in subversion: [http://svn.apache.org/repos/asf/maven/components/trunk].</p>
<p>For more information, see <a href="http://maven.apache.org/guides/development/guide-building-m2.html" class="externalLink">Building Maven</a></p></section><section>
<h3>Why does Maven compile my test classes but doesn't run them?</h3>
@@ -1175,7 +1175,7 @@ Your favorite IDE probably supports XSD
<p>(#Dependencies, Design, Patterns & Best Practices)</p></section><section>
<h3>Where to find the source code for org.apache.maven.model package?</h3>
<p>The source for the model package is generated by modello. From your maven-model source, build it and you should able to see tha java files inside /target/generated-sources directory.</p></section><section>
-<h3>List of available Maven mirrors.</h3>
+<h3>List of available Maven mirrors</h3>
<p>Here is the list of available mirrors you can use, just use one of the following mirror entries in your settings.xml</p>
<div class="source"><pre class="prettyprint linenums"><code><settings>
@@ -1509,9 +1509,9 @@ I think your choice is probably influenc
</code></pre></div></section><section>
<h3>How can I stop this “WARNING While downloading artifactId-artifactId-version This artifact has been relocated to groupId-artifactId-version”?</h3>
<p>It's probably because some other dependency has specified the dependency on artifactId:artifactId. It will only go away when that declaration is fixed in that POM.</p></section><section>
-<h3>I would like clarification on what version of the JDK is required for m2 - particularly with respect to creating Plugins.</h3>
+<h3>I would like clarification on what version of the JDK is required for m2 - particularly with respect to creating Plugins</h3>
<p>1.4 is required to run m2 there're problems when using 1.5 features in plugins. People tried and failed because qdox (used for some mojo stuff doesn't support new 1.5 language)</p></section><section>
-<h3>i'm wondering what a “snapshot” actually is.</h3>
+<h3>i'm wondering what a “snapshot” actually is</h3>
<p>A snapshot is a development version. e.g, 2.0-SNAPSHOT is thestill-in-development future 2.0.If you want to use a snapshot, just use <code><version></code> , e.g. <code><version>2.0-SNAPSHOT</version></code> . But first you must ensure that you have access to the repository containing this version.</p></section><section>
<h3>Is it possible that if I do mvn eclipse eclipse goal that my project would get disconnected from the subversion repository?</h3>
<p>1.4 is required to run m2 there're problems when using 1.5 features in plugins. People tried and failed because qdox (used for some mojo stuff doesn't support new 1.5 language)</p></section><section>
Modified: maven/website/content/guides/development/guide-documentation-style.html
==============================================================================
--- maven/website/content/guides/development/guide-documentation-style.html (original)
+++ maven/website/content/guides/development/guide-documentation-style.html Sat Feb 18 18:17:30 2023
@@ -179,7 +179,7 @@ under the License.
<h4>Example</h4>
<p>The following is an example of how the distribution management of the Maven site is configured.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
...
<distributionManagement>
<site>
Modified: maven/website/content/guides/development/guide-maven-development.html
==============================================================================
--- maven/website/content/guides/development/guide-maven-development.html (original)
+++ maven/website/content/guides/development/guide-maven-development.html Sat Feb 18 18:17:30 2023
@@ -166,7 +166,7 @@ under the License.
<p>When you find a issue you would like to work on, add a comment in the issue log so the core developers and other people looking for work know that someone is already working on it.</p></section><section>
<h3>Where's the source?</h3>
<p>See <a href="/scm.html">https://maven.apache.org/scm.html</a> for information. The Maven project uses the Apache GitBox Repositories, and all of them are dual-mirrored to <a href="https://github.com/apache/" class="externalLink">GitHub</a>.</p></section><section>
-<h3>Don't forget tests!</h3><!-- TODO move details to guide-building-maven.apt, keep only principles here -->
+<h3>Don't forget tests</h3><!-- TODO move details to guide-building-maven.apt, keep only principles here -->
<p>You will find many unit tests. If at all possible, create or modify a unit test to demonstrate the problem, and then validate your fix.</p>
<p>If you need to mock a class to write a test, use the Mockito framework. Parts of the Maven codebase predate Mockito so you will encounter existing tests that use EasyMock, PowerMock, and JMock. However, all newly written mocks should use Mockito, even if this means a module or a single class uses multiple mocking frameworks. If an existing test class has complicated legacy mock setup, you can add new Mockito based tests in a new test class. There is no requirement that all tests for a single model class must be in the same test class. It is OK to have multiple test classes per model class.</p>
Modified: maven/website/content/guides/development/guide-plugin-documentation.html
==============================================================================
--- maven/website/content/guides/development/guide-plugin-documentation.html (original)
+++ maven/website/content/guides/development/guide-plugin-documentation.html Sat Feb 18 18:17:30 2023
@@ -187,7 +187,7 @@ under the License.
<p><code><issueManagement></code> - describes the system used for reporting problems and modification requests</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<issueManagement>
<system>jira</system>
@@ -204,7 +204,7 @@ under the License.
<p><code><mailingLists></code> - lists where other users or the developers can be contacted for help and discussions</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<mailingLists>
<mailingList>
@@ -226,7 +226,7 @@ under the License.
<li><code><licenses></code> - plugin license</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<licenses>
<license>
@@ -243,7 +243,7 @@ under the License.
<li><code><scm></code> - the source code management configuration - a plugin without this would raise suspicion, might not be OSS</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<scm>
<connection>scm:svn:http://noonecares.com/some/plugin/project/trunk</connection>
@@ -258,7 +258,7 @@ under the License.
<li><code><organization></code> - the organization maintaining the plugin, just in case we need someone to blame</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<organization>
<name>Noone Care Software Foundation</name>
@@ -270,7 +270,7 @@ under the License.
<h3>Plugin Configuration Parameters</h3>
<p>The Maven Plugin Plugin is responsible for generating the Plugin Info site and needs to be added to the <code><reporting></code> section unless it is already inherited from a parent POM:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<reporting>
<plugins>
@@ -290,7 +290,7 @@ under the License.
<li>all <code>@parameter</code> fields should have a descriptive comment, informative enough that even a regular user can understand</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code> [...]
+<div class="source"><pre class="prettyprint linenums"><code class="language-java"> [...]
/**
* Put something informative here that a regular user can understand.
*
@@ -304,7 +304,7 @@ under the License.
<li>class level comment should explain what the goal does</li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code>[...]
+<div class="source"><pre class="prettyprint linenums"><code class="language-java">[...]
/**
* Everything here will show up on the top of the generated plugin info page.
*
@@ -328,7 +328,7 @@ public class ExampleMojo
<h4>Site Descriptor</h4>
<p>The site descriptor describes the navigation links and can be found in <code>src/site/site.xml</code>. Below is the suggested site descriptor template.</p>
-<div class="source"><pre class="prettyprint linenums"><code><?xml version="1.0" encoding="UTF-8"?>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><?xml version="1.0" encoding="UTF-8"?>
<project>
<body>
<menu name="Overview">
@@ -415,7 +415,7 @@ Plugin Name
<p>A well documented project always collates frequently asked questions which are usually located in <code>src/site/fml/faq.fml</code>. The example below provides a template for your FAQ:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><?xml version="1.0" encoding="UTF-8"?>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><?xml version="1.0" encoding="UTF-8"?>
<faqs id="FAQ" title="Frequently Asked Questions">
<part id="General">
<faq id="question">
@@ -450,7 +450,7 @@ Plugin Name
<p>To enable javadoc for your plugin add the following to your <code>pom.xml</code></p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<build>
[...]
@@ -482,7 +482,7 @@ Plugin Name
<p>To enable source code cross-references add the following to your <code>pom.xml</code></p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
[...]
<build>
[...]
Modified: maven/website/content/guides/development/guide-testing-development-plugins.html
==============================================================================
--- maven/website/content/guides/development/guide-testing-development-plugins.html (original)
+++ maven/website/content/guides/development/guide-testing-development-plugins.html Sat Feb 18 18:17:30 2023
@@ -169,7 +169,7 @@ under the License.
<p>Other sites may publish there own - for example, the MojoHaus project hosts theirs at <a href="https://oss.sonatype.org/content/repositories/snapshots/" class="externalLink">https://oss.sonatype.org/content/repositories/snapshots/</a></p>
<p>The first step is to include this in your project:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
...
<pluginRepositories>
<pluginRepository>
@@ -191,7 +191,7 @@ under the License.
<p>You can have Maven automatically check for updates on a given interval, for example:</p></li>
</ul>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
...
<pluginRepositories>
<pluginRepository>
@@ -208,7 +208,7 @@ under the License.
<p>If you are using the goals from the command line on a number of projects, you should include this in your <code>settings.xml</code> file instead.</p>
<p>You need to modify your <code>${user.home}/.m2/settings.xml</code> file to include two new profiles and then when you need access to the plugin snapshots use <code>-Papache</code>. The profile only needs to be enabled once so that the plugins can be downloaded into you local repository. Once in your local repository Maven can successfully resolve the dependencies and the profile no longer needs to be activated.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><settings>
...
<profiles>
<profile>
Modified: maven/website/content/guides/development/guide-testing-releases.html
==============================================================================
--- maven/website/content/guides/development/guide-testing-releases.html (original)
+++ maven/website/content/guides/development/guide-testing-releases.html Sat Feb 18 18:17:30 2023
@@ -176,7 +176,7 @@ under the License.
</ul>
<p>The repository configuration for testing a plugin will typically look something like this (it will be provided in the vote email):</p>
-<div class="source"><pre class="prettyprint linenums"><code> ...
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> ...
<pluginRepositories>
<pluginRepository>
<id>staged-releases</id>
@@ -229,7 +229,7 @@ under the License.
<p>It is also quite easy to test another staged release at a later date by reusing the repository, or adding a proxy connector and remote repository for a different staging repository.</p>
<p>If you are using the repository mirroring technique to lock down to the repository manager in your environment, you would add an additional mirror to correspond to the additional repository in the POM, such as:</p>
-<div class="source"><pre class="prettyprint linenums"><code> ...
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> ...
<mirror>
<id>staged-releases-mirror</id>
<url>http://localhost:8080/archiva/repository/staged-releases/</url>
@@ -240,7 +240,7 @@ under the License.
<h3>Using a Settings Profile</h3>
<p>If you regularly test staged releases and want to have a more convenient way to add the repository to a build without modifying your POM, you may add a profile to your <code>\~/.m2/settings.xml</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code> ...
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> ...
<profiles>
<profile>
<id>staged-releases</id>
Modified: maven/website/content/guides/getting-started/index.html
==============================================================================
--- maven/website/content/guides/getting-started/index.html (original)
+++ maven/website/content/guides/getting-started/index.html Sat Feb 18 18:17:30 2023
@@ -236,7 +236,7 @@ under the License.
</code></pre></div>
<p>Once you have executed this command, you will notice a few things have happened. First, you will notice that a directory named <code>my-app</code> has been created for the new project, and this directory contains a file named <code>pom.xml</code> that should look like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -493,7 +493,7 @@ under the License.
<h3>What is a SNAPSHOT version?</h3>
<p>Notice the value of the <strong>version</strong> tag in the <code>pom.xml</code> file shown below has the suffix: <code>-SNAPSHOT</code>.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0"
...
<groupId>...</groupId>
<artifactId>my-app</artifactId>
@@ -509,7 +509,7 @@ under the License.
<p>Whenever you want to customise the build for a Maven project, this is done by adding or reconfiguring plugins.</p>
<p>For this example, we will configure the Java compiler to allow JDK 5.0 sources. This is as simple as adding this to your POM:</p>
-<div class="source"><pre class="prettyprint linenums"><code>...
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">...
<build>
<plugins>
<plugin>
@@ -599,7 +599,7 @@ artifactId=my-app
</code></pre></div>
<p>In a unit test you could use a simple snippet of code like the following to access the resource required for testing:</p>
-<div class="source"><pre class="prettyprint linenums"><code>...
+<div class="source"><pre class="prettyprint linenums"><code class="language-java">...
// Retrieve resource
InputStream is = getClass().getResourceAsStream( "/test.properties" );
@@ -612,7 +612,7 @@ InputStream is = getClass().getResourceA
<p>Sometimes a resource file will need to contain a value that can only be supplied at build time. To accomplish this in Maven, put a reference to the property that will contain the value into your resource file using the syntax <code>${<property name>}</code>. The property can be one of the values defined in your pom.xml, a value defined in the user's settings.xml, a property defined in an external properties file, or a system property.</p>
<p>To have Maven filter resources when copying, simply set <code>filtering</code> to true for the resource directory in your <code>pom.xml</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -668,7 +668,7 @@ my.filter.value=hello!
</code></pre></div>
<p>Next, we'll add a reference to this new file in the <code>pom.xml</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -711,7 +711,7 @@ message=${my.filter.value}
</code></pre></div>
<p>the next execution of the <code>mvn process-resources</code> command will put our new property value into <code>application.properties</code>. As an alternative to defining the my.filter.value property in an external file, you could also have defined it in the <code>properties</code> section of your <code>pom.xml</code> and you'd get the same effect (notice I don't need the references to <code>src/main/filters/filter.properties</code> either):</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -760,7 +760,7 @@ command.line.prop=${command.line.prop}
<p>You've probably already noticed a <code>dependencies</code> element in the POM we've been using as an example. You have, in fact, been using an external dependency all this time, but here we'll talk about how this works in a bit more detail. For a more thorough introduction, please refer to our <a href="../introduction/introduction-to-dependency-mechanism.html">Introduction to Dependency Mechanism</a>.</p>
<p>The <code>dependencies</code> section of the pom.xml lists all of the external dependencies that our project needs in order to build (whether it needs that dependency at compile time, test time, run time, or whatever). Right now, our project is depending on JUnit only (I took out all of the resource filtering stuff for clarity):</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -787,7 +787,7 @@ command.line.prop=${command.line.prop}
<p>For more information about the dependency mechanism as a whole, see <a href="../introduction/introduction-to-dependency-mechanism.html">Introduction to Dependency Mechanism</a>.</p>
<p>With this information about a dependency, Maven will be able to reference the dependency when it builds the project. Where does Maven reference the dependency from? Maven looks in your local repository (<code>${user.home}/.m2/repository</code> is the default location) to find all dependencies. In a <a href="#how-do-i-create-a-jar-and-install-it-in-my-local-repository">previous section</a>, we installed the artifact from our project (my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed there, another project can reference that jar as a dependency simply by adding the dependency information to its pom.xml:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<groupId>com.mycompany.app</groupId>
<artifactId>my-other-app</artifactId>
@@ -806,7 +806,7 @@ command.line.prop=${command.line.prop}
<p>What about dependencies built somewhere else? How do they get into my local repository? Whenever a project references a dependency that isn't available in the local repository, Maven will download the dependency from a remote repository into the local repository. You probably noticed Maven downloading a lot of things when you built your very first project (these downloads were dependencies for the various plugins used to build the project). By default, the remote repository Maven uses can be found (and browsed) at <a href="https://repo.maven.apache.org/maven2/" class="externalLink">https://repo.maven.apache.org/maven2/</a>. You can also set up your own remote repository (maybe a central repository for your company) to use instead of or in addition to the default remote repository. For more information on repositories you can refer to the <a href="../introduction/introduction-to-repositories.html">Introduction to Repositories</a>.</p>
<p>Let's add another dependency to our project. Let's say we've added some logging to the code and need to add log4j as a dependency. First, we need to know what the groupId, artifactId, and version are for log4j. The appropriate directory on Maven Central is called <a href="https://repo.maven.apache.org/maven2/log4j/log4j/" class="externalLink">/maven2/log4j/log4j</a>. In that directory is a file called maven-metadata.xml. Here's what the maven-metadata.xml for log4j looks like:</p>
-<div class="source"><pre class="prettyprint linenums"><code><metadata>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><metadata>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.1.3</version>
@@ -828,7 +828,7 @@ command.line.prop=${command.line.prop}
<p>From this file, we can see that the groupId we want is “log4j” and the artifactId is “log4j”. We see lots of different version values to choose from; for now, we'll just use the latest version, 1.2.12 (some maven-metadata.xml files may also specify which version is the current release version: see <a href="/ref/current/maven-repository-metadata/repository-metadata.html">repository metadata reference</a>). Alongside the maven-metadata.xml file, we can see a directory corresponding to each version of the log4j library. Inside each of these, we'll find the actual jar file (e.g. log4j-1.2.12.jar) as well as a pom file (this is the pom.xml for the dependency, indicating any further dependencies it might have and other information) and another maven-metadata.xml file. There's also an md5 file corresponding to each of these, which contains an MD5 hash for these files. You can use this to authenticate the library or to figure out which version of a particular
library you may be using already.</p>
<p>Now that we know the information we need, we can add the dependency to our pom.xml:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -862,7 +862,7 @@ command.line.prop=${command.line.prop}
<p>For deploying jars to an external repository, you have to configure the repository url in the pom.xml and the authentication information for connecting to the repository in the settings.xml.</p>
<p>Here is an example using scp and username/password authentication:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -914,7 +914,7 @@ command.line.prop=${command.line.prop}
</project>
</code></pre></div>
-<div class="source"><pre class="prettyprint linenums"><code><settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
...
<servers>
@@ -952,7 +952,7 @@ command.line.prop=${command.line.prop}
</code></pre></div>
<p>Note that these must all be on a single line. This will create a directory called <code>my-webapp</code> containing the following project descriptor:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -998,7 +998,7 @@ command.line.prop=${command.line.prop}
</code></pre></div>
<p>The POM file you'll create should contain the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -1015,7 +1015,7 @@ command.line.prop=${command.line.prop}
</code></pre></div>
<p>We'll need a dependency on the JAR from the webapp, so add this to <code>my-webapp/pom.xml</code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code> ...
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> ...
<dependencies>
<dependency>
<groupId>com.mycompany.app</groupId>
@@ -1027,7 +1027,7 @@ command.line.prop=${command.line.prop}
</code></pre></div>
<p>Finally, add the following <code><parent></code> element to both of the other <code>pom.xml</code> files in the subdirectories:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>com.mycompany.app</groupId>
Modified: maven/website/content/guides/getting-started/maven-in-five-minutes.html
==============================================================================
--- maven/website/content/guides/getting-started/maven-in-five-minutes.html (original)
+++ maven/website/content/guides/getting-started/maven-in-five-minutes.html Sat Feb 18 18:17:30 2023
@@ -207,7 +207,7 @@ OS name: "windows 10", version
<h4>The POM</h4>
<p>The <code>pom.xml</code> file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -265,7 +265,7 @@ OS name: "windows 10", version
<p>By default your version of Maven might use an old version of the <code>maven-compiler-plugin</code> that is not compatible with Java 9 or later versions. To target Java 9 or later, you should at least use version 3.6.0 of the <code>maven-compiler-plugin</code> and set the <code>maven.compiler.release</code> property to the Java release you are targetting (e.g. 9, 10, 11, 12, etc.).</p>
<p>In the following example, we have configured our Maven project to use version 3.8.1 of <code>maven-compiler-plugin</code> and target Java 11:</p>
-<div class="source"><pre class="prettyprint linenums"><code> <properties>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> <properties>
<maven.compiler.release>11</maven.compiler.release>
</properties>
Modified: maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html (original)
+++ maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html Sat Feb 18 18:17:30 2023
@@ -299,7 +299,7 @@ This scope is only supported on a depend
<p>The dependency management section is a mechanism for centralizing dependency information. When you have a set of projects that inherit from a common parent, it's possible to put all information about the dependency in the common POM and have simpler references to the artifacts in the child POMs. The mechanism is best illustrated through some examples. Given these two POMs which extend the same parent:</p>
<p>Project A:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -327,7 +327,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>Project B:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -351,7 +351,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>These two example POMs share a common dependency and each has one non-trivial dependency. This information can be put in the parent POM like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencyManagement>
@@ -392,7 +392,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>Then the two child POMs become much simpler:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -412,7 +412,7 @@ This scope is only supported on a depend
</code></pre></div>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -437,7 +437,7 @@ This scope is only supported on a depend
<p>A second, and very important use of the dependency management section is to control the versions of artifacts used in transitive dependencies. As an example consider these projects:</p>
<p>Project A:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
@@ -476,7 +476,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>Project B:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<parent>
<artifactId>A</artifactId>
@@ -531,7 +531,7 @@ This scope is only supported on a depend
<p>The examples in the previous section describe how to specify managed dependencies through inheritance. However, in larger projects it may be impossible to accomplish this since a project can only inherit from a single parent. To accommodate this, projects can import managed dependencies from other projects. This is accomplished by declaring a POM artifact as a dependency with a scope of “import”.</p>
<p>Project B:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
@@ -576,7 +576,7 @@ This scope is only supported on a depend
<p>Assuming A is the POM defined in the preceding example, the end result would be the same. All of A's managed dependencies would be incorporated into B except for d since it is defined in this POM.</p>
<p>Project X:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
@@ -605,7 +605,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>Project Y:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
@@ -634,7 +634,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>Project Z:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>maven</groupId>
@@ -670,7 +670,7 @@ This scope is only supported on a depend
<p>Imports are most effective when used for defining a “library” of related artifacts that are generally part of a multiproject build. It is fairly common for one project to use one or more artifacts from these libraries. However, it has sometimes been difficult to keep the versions in the project using the artifacts in synch with the versions distributed in the library. The pattern below illustrates how a “bill of materials” (BOM) can be created for use by other projects.</p>
<p>The root of the project is the BOM POM. It defines the versions of all the artifacts that will be created in the library. Other projects that wish to use the library should import this POM into the dependencyManagement section of their POM.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -706,7 +706,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>The parent subproject has the BOM POM as its parent. It is a normal multiproject pom.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -744,7 +744,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>Next are the actual project POMs.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -790,7 +790,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>The project that follows shows how the library can now be used in another project without having to specify the dependent project's versions.</p>
-<div class="source"><pre class="prettyprint linenums"><code><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.test</groupId>
@@ -837,7 +837,7 @@ This scope is only supported on a depend
<p>Dependencies with the scope <em>system</em> are always available and are not looked up in repository. They are usually used to tell Maven about dependencies which are provided by the JDK or the VM. Thus, system dependencies are especially useful for resolving dependencies on artifacts which are now provided by the JDK, but were available as separate downloads earlier. Typical examples are the JDBC standard extensions or the Java Authentication and Authorization Service (JAAS).</p>
<p>A simple example would be:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -855,7 +855,7 @@ This scope is only supported on a depend
</code></pre></div>
<p>If your artifact is provided by the JDK's <code>tools.jar</code>, the system path would be defined as follows:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
...
<dependencies>
<dependency>
Modified: maven/website/content/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-optional-and-excludes-dependencies.html (original)
+++ maven/website/content/guides/introduction/introduction-to-optional-and-excludes-dependencies.html Sat Feb 18 18:17:30 2023
@@ -177,7 +177,7 @@ under the License.
<h4>How do I use the optional tag?</h4>
<p>A dependency is declared optional by setting the <code><optional></code> element to true in its dependency declaration:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -213,7 +213,7 @@ Project-X -> Project-A
<h4>How to use dependency exclusions</h4>
<p>Add an <code><exclusions></code> element in the <code><dependency></code> element by which the problematic jar is included.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
...
<dependencies>
@@ -250,7 +250,7 @@ Project-A
</code></pre></div>
<p>Suppose you don't want project D and its dependencies to be added to Project A's classpath because some of Project-D's dependencies are missing from the repository, and you don't need the functionality in Project-B that depends on Project-D anyway. Project-B's developers could have marked the dependency on Project-D <code><optional>true</optional></code>:</p>
-<div class="source"><pre class="prettyprint linenums"><code><dependency>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><dependency>
<groupId>sample.ProjectD</groupId>
<artifactId>ProjectD</artifactId>
<version>1.0-SNAPSHOT</version>
@@ -259,7 +259,7 @@ Project-A
</code></pre></div>
<p>Unfortunately, they didn't. As a last resort, you can exclude it on your own POM for Project-A like this:</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>sample.ProjectA</groupId>
@@ -313,7 +313,7 @@ Project-A
</code></pre></div>
<p>Exclusions work on the entire dependency graph below the point where they are declared. If you want to exclude Project-E instead of Project-D, simply change the exclusion to point at Project-E, but you don't move the exclusion down to Project-D. You cannot change Project-D's POM. If you could, you would use optional dependencies instead of exclusions, or split Project-D up into multiple subprojects, each with nothing but normal dependencies.</p>
-<div class="source"><pre class="prettyprint linenums"><code>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml">
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>sample.ProjectA</groupId>
Modified: maven/website/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-plugin-prefix-mapping.html (original)
+++ maven/website/content/guides/introduction/introduction-to-plugin-prefix-mapping.html Sat Feb 18 18:17:30 2023
@@ -175,7 +175,7 @@ under the License.
</ul>
<p>If your plugin's artifactId fits this pattern, Maven will automatically map your plugin to the correct prefix in the metadata stored within your plugin's groupId path on the repository. However, if you want to customize the prefix used to reference your plugin, you can specify the prefix directly through a configuration parameter on the <code>maven-plugin-plugin</code> in your plugin's POM:</p>
-<div class="source"><pre class="prettyprint linenums"><code><project>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
...
<build>
...
@@ -207,7 +207,7 @@ under the License.
<p>By default, Maven will search the groupId <strong>org.apache.maven.plugins</strong> for prefix-to-artifactId mappings for the plugins it needs to perform a given build. However, as previously mentioned, the user may have a need for third-party plugins. Since the Maven project is assumed to have control over the default plugin groupId, this means configuring Maven to search other groupId locations for plugin-prefix mappings.</p>
<p>As it turns out, this is simple. In the Maven settings file (per-user: <code>${user.home}/.m2/settings.xml</code>; global: <code>${maven.home}/conf/settings.xml</code>), you can provide a custom <strong>pluginGroups</strong> section, listing the plugin groupIds you want to search (each groupId goes in its own <strong>pluginGroup</strong> sub-element). For example, if my project uses a Modello model file, I might have the following in my settings:</p>
-<div class="source"><pre class="prettyprint linenums"><code><pluginGroups>
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><pluginGroups>
<pluginGroup>org.codehaus.modello</pluginGroup>
</pluginGroups>
</code></pre></div>