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/03/24 11:57:53 UTC

svn commit: r1908686 [11/13] - in /maven/website/content: ./ apache-resource-bundles/ archives/maven-2.x/ background/ developers/ developers/conventions/ developers/release/ developers/website/ docs/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2/ do...

Modified: maven/website/content/pom.html
==============================================================================
--- maven/website/content/pom.html (original)
+++ maven/website/content/pom.html Fri Mar 24 11:57:50 2023
@@ -2,16 +2,16 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/pom.apt.vm at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/pom.apt.vm at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
-    <meta name="author" content="Eric Redmond, et al.
-Karl Heinz Marbaise" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
+    <meta name="author" content="Eric Redmond, et al." />
+    <meta name="author" content="Karl Heinz Marbaise" />
     <meta name="date" content="2019-12-31" />
     <title>Maven &#x2013; POM Reference</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
@@ -50,7 +50,7 @@ Karl Heinz Marbaise" />
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">POM Reference <a href="https://github.com/apache/maven-site/tree/master/content/apt/pom.apt.vm"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="download.cgi" title="Download">Download</a></li>
@@ -193,11 +193,12 @@ Karl Heinz Marbaise" />
 <h1><a id="Introduction">Introduction</a></h1>
 <ul>
 <li><a href="/xsd/maven-4.0.0.xsd">The POM 4.0.0 XSD</a> and <a href="/ref/current/maven-model/maven.html">descriptor reference documentation</a></li></ul><section>
-<h2><a id="What_is_the_POM">What is the POM?</a></h2>
+<h2><a id="What_is_the_POM.3F">What is the POM?</a></h2>
 <p>POM stands for &quot;Project Object Model&quot;. It is an XML representation of a Maven project held in a file named <code>pom.xml</code>. When in the presence of Maven folks, speaking of a project is speaking in the philosophical sense, beyond a mere collection of files containing code. A project contains configuration files, as well as the developers involved and the roles they play, the defect tracking system, the organization and licenses, the URL of where the project lives, the project's dependencies, and all of the other little pieces that come into play to give code life. It is a one-stop-shop for all things concerning the project. In fact, in the Maven world, a project does not need to contain any code at all, merely a <code>pom.xml</code>.</p></section><section>
 <h2><a id="Quick_Overview">Quick Overview</a></h2>
 <p>This is a listing of the elements directly under the POM's project element. Notice that <code>modelVersion</code> contains 4.0.0. That is currently the only supported POM version, and is always required.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
@@ -239,7 +240,8 @@ Karl Heinz Marbaise" />
 &lt;/project&gt;</pre></div></section></section><section>
 <h1><a id="The_Basics">The Basics</a></h1>
 <p>The POM contains all necessary information about a project, as well as configurations of plugins to be used during the build process. It is the declarative manifestation of the &quot;who&quot;, &quot;what&quot;, and &quot;where&quot;, while the build lifecycle is the &quot;when&quot; and &quot;how&quot;. That is not to say that the POM cannot affect the flow of the lifecycle - it can. For example, by configuring the <code>maven-antrun-plugin</code>, one can embed Apache Ant tasks inside of the POM. It is ultimately a declaration, however. Whereas a <code>build.xml</code> tells Ant precisely what to do when it is run (procedural), a POM states its configuration (declarative). If some external force causes the lifecycle to skip the Ant plugin execution, it does not stop the plugins that are executed from doing their magic. This is unlike a <code>build.xml</code> file, where tasks are almost always dependant on the lines executed before it.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
@@ -256,7 +258,8 @@ Karl Heinz Marbaise" />
 <p>The three elements given above point to a specific version of a project, letting Maven know <i>who</i> we are dealing with, and <i>when</i> in its software lifecycle we want them.</p></section><section>
 <h2><a id="Packaging">Packaging</a></h2>
 <p>Now that we have our address structure of <code>groupId:artifactId:version</code>, there is one more standard label to give us a really complete <i>what</i>: that is the project's packaging. In our case, the example POM for <code>org.codehaus.mojo:my-project:1.0</code> defined above will be packaged as a <code>jar</code>. We could make it into a <code>war</code> by declaring a different packaging:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;packaging&gt;war&lt;/packaging&gt;
@@ -269,7 +272,8 @@ Karl Heinz Marbaise" />
 <p>Maven solves both problems through a common local repository from which to link projects correctly, versions and all.</p><section>
 <h3><a id="Dependencies">Dependencies</a></h3>
 <p>The cornerstone of the POM is its <a href="/ref/current/maven-model/maven.html#class_dependency">dependency</a> list. Most projects depend on others to build and run correctly. If all Maven does for you is manage this list, you have gained a lot. Maven downloads and links the dependencies on compilation, as well as on other goals that require them. As an added bonus, Maven brings in the dependencies of those dependencies (transitive dependencies), allowing your list to focus solely on the dependencies your project requires.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;dependencies&gt;
@@ -294,7 +298,7 @@ Karl Heinz Marbaise" />
 <p>There are times, unfortunately, when a project cannot be downloaded from the central Maven repository. For example, a project may depend upon a jar that has a closed-source license which prevents it from being in a central repository. There are three methods for dealing with this scenario.</p>
 <ol style="list-style-type: decimal">
 <li>Install the dependency locally using the install plugin. The method is the simplest recommended method. For example:
-<div>
+<div class="verbatim">
 <pre>mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -DartifactId=non-maven-proj -Dversion=1 -Dpackaging=jar</pre></div>
 <p>Notice that an address is still required, only this time you use the command line and the install plugin will create a POM for you with the given address.</p></li>
 <li>Create your own repository and deploy it there. This is a favorite method for companies with an intranet and need to be able to keep everyone in synch. There is a Maven goal called <code>deploy:deploy-file</code> which is similar to the <code>install:install-file</code> goal (read the plugin's goal page for more information).</li>
@@ -377,10 +381,10 @@ Karl Heinz Marbaise" />
 <p>Note: As <code>2.0-rc1</code> &lt; <code>2.0</code>, the version requirement <code>[1.0,2.0)</code> excludes <code>2.0</code> but includes version <code>2.0-rc1</code>, which is contrary to what most people expect. In addition, Gradle interprets it differently, resulting in different dependency trees for the same POM. If the intention is to restrict it to <i>1.*</i> versions, the better version requirement is <code>[1,1.999999)</code>.</p></li></ul></section><section>
 <h4><a id="Version_Order_Testing">Version Order Testing</a>:</h4>
 <p>The maven distribution includes a tool to check version order. It was used to produce the examples in the previous paragraphs. Feel free to run it yourself when in doubt. You can run it like this:</p>
-<div>
+<div class="verbatim">
 <pre>java -jar ${MAVEN_HOME}/lib/maven-artifact-3.9.1.jar [versions...]</pre></div>
 <p>example:</p>
-<div>
+<div class="verbatim">
 <pre>$ java -jar ./lib/maven-artifact-3.9.1.jar  1 2 1.1
 Display parameters as parsed by Maven (in canonical form and as a list of tokens) and comparison result:
 1. 1 -&gt; 1; tokens: [1]
@@ -390,7 +394,8 @@ Display parameters as parsed by Maven (i
 3. 1.1 -&gt; 1.1; tokens: [1, 1]</pre></div></section><section>
 <h4><a id="Exclusions">Exclusions</a></h4>
 <p>It is sometimes useful to limit a dependency's transitive dependencies. A dependency may have incorrectly specified scopes, or dependencies that conflict with other dependencies in your project. Exclusions tell Maven not to include a specified artifact in the classpath even if it is a dependency of one or more of this project's dependencies (a transitive dependency). For example, <code>maven-embedder</code> depends on <code>maven-core</code>. Suppose you want to depend on maven-embedder but do not want to include maven-core or its dependencies in the classpath. Then add <code>maven-core</code> as an <code>exclusion</code> in the element that declares the dependency on maven-embedder:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;dependencies&gt;
@@ -411,7 +416,8 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div>
 <p>This only removes the path to maven-core from this one dependency. If maven-core appears as a direct or transitive dependency elsewhere in the POM, it can still be added to the classpath.</p>
 <p>Wildcard excludes make it easy to exclude all of a dependency's transitive dependencies. In the case below, you may be working with the maven-embedder and you want to manage the dependencies you use, so you exclude all the transitive dependencies:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;dependencies&gt;
@@ -434,7 +440,8 @@ Display parameters as parsed by Maven (i
 <li><b>exclusions</b>: Exclusions contain one or more <code>exclusion</code> elements, each containing a <code>groupId</code> and <code>artifactId</code> denoting a dependency to exclude. Unlike <code>optional</code>, which may or may not be installed and used, <code>exclusions</code> actively remove artifacts from the dependency tree.</li></ul></section></section><section>
 <h3><a id="Inheritance">Inheritance</a></h3>
 <p>One powerful addition that Maven brings to build management is the concept of project inheritance. Although in build systems such as Ant inheritance can be simulated, Maven makes project inheritance explicit in the project object model.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
@@ -475,7 +482,8 @@ Display parameters as parsed by Maven (i
 <li>artifactId</li>
 <li>name</li>
 <li>prerequisites</li></ul>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
@@ -492,7 +500,8 @@ Display parameters as parsed by Maven (i
 <p>To see inheritance in action, just have a look at the <a class="externalLink" href="https://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?view=markup">ASF</a> or <a class="externalLink" href="https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=markup">Maven</a> parent POM's.</p><section>
 <h4><a id="The_Super_POM">The Super POM</a></h4>
 <p>Similar to the inheritance of objects in object oriented programming, POMs that extend a parent POM inherit certain values from that parent. Moreover, just as Java objects ultimately inherit from <code>java.lang.Object</code>, all Project Object Models inherit from a base Super POM. The snippet below is the Super POM for Maven 3.5.4.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project&gt;
+<div class="verbatim source">
+<pre>&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;repositories&gt;
@@ -628,7 +637,8 @@ Display parameters as parsed by Maven (i
 <p>Note that the version and scope of artifacts which are incorporated from transitive dependencies are also controlled by version specifications in a dependency management section. This can lead to unexpected consequences. Consider a case in which your project uses two dependences, <code>dep1</code> and <code>dep2</code>. <code>dep2</code> in turn also uses <code>dep1</code>, and requires a particular minimum version to function. If you then use <code>dependencyManagement</code> to specify an older version, <code>dep2</code> will be forced to use the older version, and fail. So, you must be careful to check the entire dependency tree to avoid this problem; <code>mvn dependency:tree</code> is helpful.</p></li></ul></section></section><section>
 <h3><a id="Aggregation">Aggregation</a> (or Multi-Module)</h3>
 <p>A project with modules is known as a multi-module, or aggregator project. Modules are projects that this POM lists, and are executed as a group. A <code>pom</code> packaged project may aggregate the build of a set of projects by listing them as modules, which are relative paths to the directories or the POM files of those projects.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
@@ -649,7 +659,8 @@ Display parameters as parsed by Maven (i
 <p>Inheritance and aggregation create a nice dynamic to control builds through a single, high-level POM. You often see projects that are both parents and aggregators. For example, the entire Maven core runs through a single base POM <a class="externalLink" href="https://svn.apache.org/viewvc/maven/maven-3/trunk/pom.xml?view=markup"><code>org.apache.maven:maven</code></a>, so building the Maven project can be executed by a single command: <code>mvn compile</code>. However, an aggregator project and a parent project are both POM projects, they are not one and the same and should not be confused. A POM project may be inherited from - but does not necessarily have - any modules that it aggregates. Conversely, a POM project may aggregate projects that do not inherit from it.</p></section></section></section><section>
 <h2><a id="Properties">Properties</a></h2>
 <p>Properties are the last required piece to understand POM basics. Maven properties are value placeholders, like properties in Ant. Their values are accessible anywhere within a POM by using the notation <code>${X}</code>, where <code>X</code> is the property. Or they can be used by plugins as default values, for example:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project&gt;
+<div class="verbatim source">
+<pre>&lt;project&gt;
   ...
   &lt;properties&gt;
     &lt;maven.compiler.source&gt;1.7&lt;/maven.compiler.source&gt;
@@ -674,7 +685,8 @@ Display parameters as parsed by Maven (i
 <h2><a id="Build">Build</a></h2>
 <p>According to the POM 4.0.0 XSD, the <code>build</code> element is conceptually divided into two parts: there is a <code>BaseBuild</code> type which contains the set of elements common to both <code>build</code> elements (the top-level build element under <code>project</code> and the build element under <code>profiles</code>, covered below); and there is the <code>Build</code> type, which contains the <code>BaseBuild</code> set as well as more elements for the top level definition. Let us begin with an analysis of the common elements between the two.</p>
 <p><i>Note: These different</i> <code>build</code> <i>elements may be denoted &quot;project build&quot; and &quot;profile build&quot;.</i></p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;!-- &quot;Project Build&quot; contains more elements than just the BaseBuild set --&gt;
@@ -689,7 +701,7 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div><section>
 <h3>The <a id="BaseBuild_Element">BaseBuild Element</a> Set</h3>
 <p><code>BaseBuild</code> is exactly as it sounds: the base set of elements between the two <code>build</code> elements in the POM.</p>
-<div>
+<div class="verbatim">
 <pre>&lt;build&gt;
   &lt;defaultGoal&gt;install&lt;/defaultGoal&gt;
   &lt;directory&gt;${basedir}/target&lt;/directory&gt;
@@ -708,7 +720,8 @@ Display parameters as parsed by Maven (i
 <h4><a id="Resources">Resources</a></h4>
 <p>Another feature of <code>build</code> elements is specifying where resources exist within your project. Resources are not (usually) code. They are not compiled, but are items meant to be bundled within your project or used for various other reasons, such as code generation.</p>
 <p>For example, a Plexus project requires a <code>configuration.xml</code> file (which specifies component configurations to the container) to live within the <code>META-INF/plexus</code> directory. Although we could just as easily place this file within <code>src/main/resources/META-INF/plexus</code>, we want instead to give Plexus its own directory of <code>src/main/plexus</code>. In order for the JAR plugin to bundle the resource correctly, you would specify resources similar to the following:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;build&gt;
     ...
@@ -740,7 +753,8 @@ Display parameters as parsed by Maven (i
 <li><b>excludes</b>: The same structure as <code>includes</code>, but specifies which files to ignore. In conflicts between <code>include</code> and <code>exclude</code>, <code>exclude</code> wins.</li>
 <li><b>testResources</b>: The <code>testResources</code> element block contains <code>testResource</code> elements. Their definitions are similar to <code>resource</code> elements, but are naturally used during test phases. The one difference is that the default (Super POM defined) test resource directory for a project is <code>${basedir}/src/test/resources</code>. Test resources are not deployed.</li></ul></section><section>
 <h4><a id="Plugins">Plugins</a></h4>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;build&gt;
     ...
@@ -769,7 +783,8 @@ Display parameters as parsed by Maven (i
 <ul>
 <li><a id="default_configuration_inheritance"><b>default configuration inheritance</b></a>:
 <p>To illustrate, consider the following fragment from a parent POM:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;plugin&gt;
+<div class="verbatim source">
+<pre>&lt;plugin&gt;
   &lt;groupId&gt;my.group&lt;/groupId&gt;
   &lt;artifactId&gt;my-plugin&lt;/artifactId&gt;
   &lt;configuration&gt;
@@ -783,7 +798,8 @@ Display parameters as parsed by Maven (i
   &lt;/configuration&gt;
 &lt;/plugin&gt;</pre></div>
 <p>And consider the following plugin configuration from a project that uses that parent as its parent:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;plugin&gt;
+<div class="verbatim source">
+<pre>&lt;plugin&gt;
   &lt;groupId&gt;my.group&lt;/groupId&gt;
   &lt;artifactId&gt;my-plugin&lt;/artifactId&gt;
   &lt;configuration&gt;
@@ -797,7 +813,8 @@ Display parameters as parsed by Maven (i
 &lt;/plugin&gt;</pre></div>
 <p>The default behavior is to merge the content of the <b>configuration</b> element according to element name. If the child POM has a particular element, that value becomes the effective value. if the child POM does not have an element, but the parent does, the parent value becomes the effective value. Note that this is purely an operation on XML; no code or configuration of the plugin itself is involved. Only the elements, not their values, are involved.</p>
 <p>Applying those rules to the example, Maven comes up with:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;plugin&gt;
+<div class="verbatim source">
+<pre>&lt;plugin&gt;
   &lt;groupId&gt;my.group&lt;/groupId&gt;
   &lt;artifactId&gt;my-plugin&lt;/artifactId&gt;
   &lt;configuration&gt;
@@ -813,7 +830,8 @@ Display parameters as parsed by Maven (i
 <li><a id="advanced_configuration_inheritance"><b>advanced configuration inheritance</b></a>: <code>combine.children</code> and <code>combine.self</code>
 <p>You can control how child POMs inherit configuration from parent POMs by adding attributes to the children of the <b>configuration</b> element. The attributes are <code>combine.children</code> and <code>combine.self</code>. Use these attributes in a child POM to control how Maven combines plugin configuration from the parent with the explicit configuration in the child.</p>
 <p>Here is the child configuration with illustrations of the two attributes:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;configuration&gt;
+<div class="verbatim source">
+<pre>&lt;configuration&gt;
   &lt;items combine.children=&quot;append&quot;&gt;
     &lt;!-- combine.children=&quot;merge&quot; is the default --&gt;
     &lt;item&gt;child-1&lt;/item&gt;
@@ -824,7 +842,8 @@ Display parameters as parsed by Maven (i
   &lt;/properties&gt;
 &lt;/configuration&gt;</pre></div>
 <p>Now, the effective result is the following:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;configuration&gt;
+<div class="verbatim source">
+<pre>&lt;configuration&gt;
   &lt;items combine.children=&quot;append&quot;&gt;
     &lt;item&gt;parent-1&lt;/item&gt;
     &lt;item&gt;parent-2&lt;/item&gt;
@@ -840,7 +859,8 @@ Display parameters as parsed by Maven (i
 <li><b>dependencies</b>: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via <code>exclusions</code>, or by altering the version of a required dependency. See above under <b>Dependencies</b> for more information.</li>
 <li><b>executions</b>: It is important to keep in mind that a plugin may have multiple goals. Each goal may have a separate configuration, possibly even binding a plugin's goal to a different phase altogether. <code>executions</code> configure the <code>execution</code> of a plugin's goals.
 <p>For example, suppose you wanted to bind the <code>antrun:run</code> goal to the <code>verify</code> phase. We want the task to echo the build directory, as well as avoid passing on this configuration to its children (assuming it is a parent) by setting <code>inherited</code> to <code>false</code>. You would get an <code>execution</code> like this:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;build&gt;
@@ -869,7 +889,7 @@ Display parameters as parsed by Maven (i
   &lt;/build&gt;
 &lt;/project&gt;</pre></div>
 <ul>
-<li><b>id</b>: Self explanatory. It specifies this execution block between all of the others. When the phase is run, it will be shown in the form: <code>[plugin:goal <a id="execution:_id">execution: id</a>]</code>. In the case of this example: <code>[antrun:run <a id="execution:_echodir">execution: echodir</a>]</code></li>
+<li><b>id</b>: Self explanatory. It specifies this execution block between all of the others. When the phase is run, it will be shown in the form: <code>[plugin:goal <a id="execution.3A_id">execution: id</a>]</code>. In the case of this example: <code>[antrun:run <a id="execution.3A_echodir">execution: echodir</a>]</code></li>
 <li><b>goals</b>: Like all pluralized POM elements, this contains a list of singular elements. In this case, a list of plugin <code>goals</code> which are being specified by this <code>execution</code> block.</li>
 <li><b>phase</b>: This is the phase that the list of goals will execute in. This is a very powerful option, allowing one to bind any goal to any phase in the build lifecycle, altering the default behavior of Maven.</li>
 <li><b>inherited</b>: Like the <code>inherited</code> element above, setting this to false will suppress Maven from passing this execution onto its children. This element is only meaningful to parent POMs.</li>
@@ -877,7 +897,8 @@ Display parameters as parsed by Maven (i
 <h4><a id="Plugin_Management">Plugin Management</a></h4>
 <ul>
 <li><b>pluginManagement</b>: is an element that is seen along side plugins. Plugin Management contains plugin elements in much the same way, except that rather than configuring plugin information for this particular project build, it is intended to configure project builds that inherit from this one. However, this only configures plugins that are actually referenced within the plugins element in the children or in the current POM. The children have every right to override <code>pluginManagement</code> definitions.</li></ul>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;build&gt;
@@ -907,7 +928,8 @@ Display parameters as parsed by Maven (i
   &lt;/build&gt;
 &lt;/project&gt;</pre></div>
 <p>If we added these specifications to the plugins element, they would apply only to a single POM. However, if we apply them under the <code>pluginManagement</code> element, then this POM <i>and all inheriting POMs</i> that add the <code>maven-jar-plugin</code> to the build will get the <code>pre-process-classes</code> execution as well. So rather than the above mess included in every child <code>pom.xml</code>, only the following is required:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;build&gt;
@@ -925,7 +947,8 @@ Display parameters as parsed by Maven (i
 <p>The <code>Build</code> type in the XSD denotes those elements that are available only for the &quot;project build&quot;. Despite the number of extra elements (six), there are really only two groups of elements that project build contains that are missing from the profile build: directories and extensions.</p><section>
 <h4><a id="Directories">Directories</a></h4>
 <p>The set of directory elements live in the parent build element, which set various directory structures for the POM as a whole. Since they do not exist in profile builds, these cannot be altered by profiles.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;build&gt;
@@ -940,7 +963,8 @@ Display parameters as parsed by Maven (i
 <p>If the values of a <code>*Directory</code> element above is set as an absolute path (when their properties are expanded) then that directory is used. Otherwise, it is relative to the base build directory: <code>${basedir}</code>. <b>Please note that the</b> <code>scriptSourceDirectory</code> <b>is nowhere used in Maven and is obsolete</b>.</p></section><section>
 <h4><a id="Extensions">Extensions</a></h4>
 <p>Extensions are a list of artifacts that are to be used in this build. They will be included in the running build's classpath. They can enable extensions to the build process (such as add an ftp provider for the Wagon transport mechanism), as well as make plugins active which make changes to the build lifecycle. In short, extensions are artifacts that are activated during build. The extensions do not have to actually do anything nor contain a Mojo. For this reason, extensions are excellent for specifying one out of multiple implementations of a common plugin interface.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;build&gt;
@@ -958,7 +982,8 @@ Display parameters as parsed by Maven (i
 <h2><a id="Reporting">Reporting</a></h2>
 <p>Reporting contains the elements that correspond specifically for the <code>site</code> generation phase. Certain Maven plugins can generate reports defined and configured under the reporting element, for example: generating Javadoc reports. Much like the build element's ability to configure plugins, reporting commands the same ability. The glaring difference is that rather than fine-grained control of plug-in goals within the executions block, reporting configures goals within <code>reportSet</code> elements. And the subtler difference is that a plugin <code>configuration</code> under the <code>reporting</code> element works as <code>build</code> plugin <code>configuration</code>, although the opposite is not true (a <code>build</code> plugin <code>configuration</code> does not affect a <code>reporting</code> plugin).</p>
 <p>Possibly the only item under the <code>reporting</code> element that would not be familiar to someone who understood the <code>build</code> element is the Boolean <code>excludeDefaults</code> element. This element signifies to the site generator to exclude reports normally generated by default. When a site is generated via the <code>site</code> build cycle, a <i>Project Info</i> section is placed in the left-hand menu, chock full of reports, such as the <b>Project Team</b> report or <b>Dependencies</b> list report. These report goals are generated by <code>maven-project-info-reports-plugin</code>. Being a plugin like any other, it may also be suppressed in the following, more verbose, way, which effectively turns off project-info reports.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;reporting&gt;
@@ -979,7 +1004,8 @@ Display parameters as parsed by Maven (i
 <h3><a id="Report_Sets">Report Sets</a></h3>
 <p>It is important to keep in mind that an individual plugin may have multiple goals. Each goal may have a separate configuration. Report sets configure execution of a report plugin's goals. Does this sound familiar - deja-vu? The same thing was said about build's <code>execution</code> element with one difference: you cannot bind a report to another phase. Sorry.</p>
 <p>For example, suppose you wanted to configure the <code>javadoc:javadoc</code> goal to link to &quot;<a class="externalLink" href="http://java.sun.com/j2se/1.5.0/docs/api/">http://java.sun.com/j2se/1.5.0/docs/api/</a>&quot;, but only the <code>javadoc</code> goal (not the goal <code>maven-javadoc-plugin:jar</code>). We would also like this configuration passed to its children, and set <code>inherited</code> to true. The <code>reportSet</code> would resemble the following:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;reporting&gt;
@@ -1014,7 +1040,8 @@ Display parameters as parsed by Maven (i
 <li><b>url</b>: The project's home page.</li>
 <li><b>inceptionYear</b>: The year the project was first created. </li></ul><section>
 <h2><a id="Licenses">Licenses</a></h2>
-<div class="source"><pre class="prettyprint linenums">&lt;licenses&gt;
+<div class="verbatim source">
+<pre>&lt;licenses&gt;
   &lt;license&gt;
     &lt;name&gt;Apache-2.0&lt;/name&gt;
     &lt;url&gt;https://www.apache.org/licenses/LICENSE-2.0.txt&lt;/url&gt;
@@ -1028,7 +1055,8 @@ Display parameters as parsed by Maven (i
 <li><b>distribution</b>: This describes how the project may be legally distributed. The two stated methods are repo (they may be downloaded from a Maven repository) or manual (they must be manually installed).</li></ul></section><section>
 <h2><a id="Organization">Organization</a></h2>
 <p>Most projects are run by some sort of organization (business, private group, etc.). Here is where the most basic information is set.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;organization&gt;
@@ -1038,7 +1066,8 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div></section><section>
 <h2><a id="Developers">Developers</a></h2>
 <p>All projects consist of files that were created, at some time, by a person. Like the other systems that surround a project, so to do the people involved with a project have a stake in the project. Developers are presumably members of the project's core development. Note that, although an organization may have many developers (programmers) as members, it is not good form to list them all as developers, but only those who are immediately responsible for the code. A good rule of thumb is, if the person should not be contacted about the project, they do not need to be listed here.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;developers&gt;
@@ -1069,7 +1098,8 @@ Display parameters as parsed by Maven (i
 <li><b>properties</b>: This element is where any other properties about the person goes. For example, a link to a personal image or an instant messenger handle. Different plugins may use these properties, or they may simply be for other developers who read the POM.</li></ul></section><section>
 <h2><a id="Contributors">Contributors</a></h2>
 <p>Contributors are like developers yet play an ancillary role in a project's lifecycle. Perhaps the contributor sent in a bug fix, or added some important documentation. A healthy open source project will likely have more contributors than developers.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;contributors&gt;
@@ -1094,7 +1124,8 @@ Display parameters as parsed by Maven (i
 <h1><a id="Environment_Settings">Environment Settings</a></h1><section>
 <h2><a id="Issue_Management">Issue Management</a></h2>
 <p>This defines the defect tracking system (<i>Bugzilla</i>, <i>TestTrack</i>, <i>ClearQuest</i>, etc) used. Although there is nothing stopping a plugin from using this information for something, it's primarily used for generating project documentation.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;issueManagement&gt;
@@ -1105,7 +1136,8 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div></section><section>
 <h2><a id="Continuous_Integration_Management">Continuous Integration Management</a></h2>
 <p>Continuous integration build systems based upon triggers or timings (such as, hourly or daily) have grown in favor over manual builds in the past few years. As build systems have become more standardized, so have the systems that run the trigger those builds. Although the majority of the configuration is up to the specific program used (Continuum, Cruise Control, etc.), there are a few configurations which may take place within the POM. Maven has captured a few of the recurring settings within the set of notifier elements. A notifier is the manner in which people are notified of certain build statuses. In the following example, this POM is setting a notifier of type <code>mail</code> (meaning email), and configuring the email address to use on the specified triggers <code>sendOnError</code>, <code>sendOnFailure</code>, and not <code>sendOnSuccess</code> or <code>sendOnWarning</code>.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;ciManagement&gt;
@@ -1126,7 +1158,8 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div></section><section>
 <h2><a id="Mailing_Lists">Mailing Lists</a></h2>
 <p>Mailing lists are a great tool for keeping in touch with people about a project. Most mailing lists are for developers and users.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;mailingLists&gt;
@@ -1149,7 +1182,8 @@ Display parameters as parsed by Maven (i
 <li><b>post</b>: The email address which one would use in order to post to the mailing list. Note that not all mailing lists have the ability to post to (such as a build failure list).</li></ul></section><section>
 <h2><a id="SCM">SCM</a></h2>
 <p>SCM (Software Configuration Management, also called Source Code/Control Management or, succinctly, version control) is an integral part of any healthy project. If your Maven project uses an SCM system (it does, doesn't it?) then here is where you would place that information into the POM.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;scm&gt;
@@ -1162,17 +1196,18 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div>
 <ul>
 <li><b>connection</b>, <b>developerConnection</b>: The two connection elements convey to how one is to connect to the version control system through Maven. Where connection requires read access for Maven to be able to find the source code (for example, an update), developerConnection requires a connection that will give write access. The Maven project has spawned another project named Maven SCM, which creates a common API for any SCMs that wish to implement it. The most popular are CVS and Subversion, however, there is a growing list of other supported <a href="/scm/scms-overview.html">SCMs</a>. All SCM connections are made through a common URL structure.
-<div>
+<div class="verbatim">
 <pre>scm:[provider]:[provider_specific]</pre></div>
 <p>Where provider is the type of SCM system. For example, connecting to a CVS repository may look like this:</p>
-<div>
+<div class="verbatim">
 <pre>scm:cvs:pserver:127.0.0.1:/cvs/root:my-project</pre></div></li>
 <li><b>tag</b>: Specifies the tag that this project lives under. HEAD (meaning, the SCM root) is the default.</li>
 <li><b>url</b>: A publicly browsable repository. For example, via ViewCVS.</li></ul></section><section>
 <h2><a id="Prerequisites">Prerequisites</a></h2>
 <p>The POM may have certain prerequisites in order to execute correctly. The only element that exists as a prerequisite in POM 4.0.0 is the <code>maven</code> element, which takes a minimum version number.</p>
 <p>Use <a href="/enforcer/enforcer-rules/requireMavenVersion.html"> Maven Enforcer Plugin's <code>requireMavenVersion</code> rule</a>, or other rules for <b>build-time</b> prerequisites. For packaging <code>maven-plugin</code> this is still used at <b>run-time</b> to make sure that the minimum Maven version for the plugin is met (but only in the pom.xml of the referenced plugin).</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;prerequisites&gt;
@@ -1183,7 +1218,8 @@ Display parameters as parsed by Maven (i
 <h2><a id="Repositories">Repositories</a></h2>
 <p>Repositories are collections of artifacts which adhere to the Maven repository directory layout. In order to be a Maven repository artifact, a POM file must live within the structure <code>$BASE_REPO/groupId/artifactId/version/artifactId-version.pom</code>. <code>$BASE_REPO</code> can be local (file structure) or remote (base URL); the remaining layout will be the same. Repositories exist as a place to collect and store artifacts. Whenever a project has a dependency upon an artifact, Maven will first attempt to use a local copy of the specified artifact. If that artifact does not exist in the local repository, it will then attempt to download from a remote repository. The repository elements within a POM specify those alternate repositories to search.</p>
 <p>The repository is one of the most powerful features of the Maven community. By default Maven searches the central repository at <a class="externalLink" href="https://repo.maven.apache.org/maven2/">https://repo.maven.apache.org/maven2/</a>. Additional repositories can be configured in the pom.xml `repositories` element. </p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;repositories&gt;
@@ -1219,7 +1255,8 @@ Display parameters as parsed by Maven (i
 <p>Repositories are home to two major types of artifacts. The first are artifacts that are used as dependencies of other artifacts. These are the majority of artifacts that reside within central. The other type of artifact is plugins. Maven plugins are themselves a special type of artifact. Because of this, plugin repositories may be separated from other repositories (although, I have yet to hear a convincing argument for doing so). In any case, the structure of the <code>pluginRepositories</code> element block is similar to the <code>repositories</code> element. The <code>pluginRepository</code> elements each specify a remote location of where Maven can find new plugins.</p></section><section>
 <h2><a id="Distribution_Management">Distribution Management</a></h2>
 <p>Distribution management acts precisely as it sounds: it manages the distribution of the artifact and supporting files generated throughout the build process. Starting with the last elements first:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;distributionManagement&gt;
@@ -1240,7 +1277,8 @@ Display parameters as parsed by Maven (i
 <li><b>verified</b>: This project has been verified, and should be considered finalized.</li></ul></li></ul><section>
 <h3><a id="Repository">Repository</a></h3>
 <p>Whereas the repositories element specifies in the POM the location and manner in which Maven may download remote artifacts for use by the current project, distributionManagement specifies where (and how) this project will get to a remote repository when it is deployed. The repository elements will be used for snapshot distribution if the snapshotRepository is not defined.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;distributionManagement&gt;
@@ -1269,7 +1307,8 @@ Display parameters as parsed by Maven (i
 <li><b>layout</b>: These are the same types and purpose as the layout element defined in the repository element. They are <code>default</code> and <code>legacy</code>.</li></ul></section><section>
 <h3><a id="Site_Distribution">Site Distribution</a></h3>
 <p>More than distribution to the repositories, <code>distributionManagement</code> is responsible for defining how to deploy the project's site and documentation.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;distributionManagement&gt;
@@ -1286,7 +1325,8 @@ Display parameters as parsed by Maven (i
 <ul>
 <li><b>id</b>, <b>name</b>, <b>url</b>: These elements are similar to their counterparts above in the <code>distributionManagement</code> <code>repository</code> element.</li></ul></section><section>
 <h3><a id="Relocation">Relocation</a></h3>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot;1 xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot;1 xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;distributionManagement&gt;
@@ -1304,7 +1344,8 @@ Display parameters as parsed by Maven (i
 <p>Projects are not static; they are living things (or dying things, as the case may be). A common thing that happens as projects grow, is that they are forced to move to more suitable quarters. For example, when your next wildly successful open source project moves under the Apache umbrella, it would be good to give users a heads-up that the project is being renamed to <code>org.apache:my-project:1.0</code>. Besides specifying the new address, it is also good form to provide a message explaining why.</p></section></section><section>
 <h2><a id="Profiles">Profiles</a></h2>
 <p>A new feature of the POM 4.0 is the ability of a project to change settings depending on the environment where it is being built. A <code>profile</code> element contains both an optional activation (a profile trigger) and the set of changes to be made to the POM if that profile has been activated. For example, a project built for a test environment may point to a different database than that of the final deployment. Or dependencies may be pulled from different repositories based upon the JDK version used. The elements of profiles are as follows:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;profiles&gt;
@@ -1324,7 +1365,8 @@ Display parameters as parsed by Maven (i
 &lt;/project&gt;</pre></div><section>
 <h3><a id="Activation">Activation</a></h3>
 <p>Activations are the key of a profile. The power of a profile comes from its ability to modify the basic POM only under certain circumstances. Those circumstances are specified via an <code>activation</code> element.</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source">
+<pre>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   ...
   &lt;profiles&gt;
@@ -1365,7 +1407,7 @@ Display parameters as parsed by Maven (i
 <li><b>file</b>: Finally, a given filename may activate the <code>profile</code> by the <code>existence</code> of a file, or if it is <code>missing</code>. <b>NOTE</b>: interpolation for this element is limited to <code>${basedir}</code>, System properties and request properties.</li></ul>
 <p>The <code>activation</code> element is not the only way that a <code>profile</code> may be activated. The <code>settings.xml</code> file's <code>activeProfile</code> element may contain the profile's <code>id</code>. They may also be activated explicitly through the command line via a comma separated list after the <code>-P</code> flag (e.g. <code>-P codecoverage</code>).</p>
 <p><i>To see which profile will activate in a certain build, use the</i> <code>maven-help-plugin</code>.</p>
-<div>
+<div class="verbatim">
 <pre>mvn help:active-profiles</pre></div></section><section>
 <h3><a id="The_BaseBuild_Element_Set">The BaseBuild Element Set</a> <i>(revisited)</i></h3>
 <p>As mentioned above, the reason for the two types of build elements reside in the fact that it does not make sense for a profile to configure build directories or extensions as it does in the top level of the POM. Reguardless of in which environment the project is built, some values will remain constant, such as the directory structure of the source code. <i>If you find your project needing to keep two sets of code for different environments, it may be prudent to investigate refactoring the project into two or more separate projects.</i></p></section></section></section><section>

Modified: maven/website/content/pom/index.html
==============================================================================
--- maven/website/content/pom/index.html (original)
+++ maven/website/content/pom/index.html Fri Mar 24 11:57:50 2023
@@ -2,17 +2,17 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/pom/index.apt.vm at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/pom/index.apt.vm at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
-    <meta name="author" content="Hervé Boutemy
-Dennis Lundberg
-Karl Heinz Marbaise" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
+    <meta name="author" content="Hervé Boutemy" />
+    <meta name="author" content="Dennis Lundberg" />
+    <meta name="author" content="Karl Heinz Marbaise" />
     <meta name="date" content="2015-11-01" />
     <title>Maven &#x2013; Parent POMs</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
@@ -51,7 +51,7 @@ Karl Heinz Marbaise" />
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Parent POMs <a href="https://github.com/apache/maven-site/tree/master/content/apt/pom/index.apt.vm"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>

Modified: maven/website/content/privacy-policy.html
==============================================================================
--- maven/website/content/privacy-policy.html (original)
+++ maven/website/content/privacy-policy.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/privacy-policy.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/privacy-policy.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Privacy Policy</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="./css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Privacy Policy <a href="https://github.com/apache/maven-site/tree/master/content/markdown/privacy-policy.md"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="download.cgi" title="Download">Download</a></li>

Modified: maven/website/content/project-faq.html
==============================================================================
--- maven/website/content/project-faq.html (original)
+++ maven/website/content/project-faq.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/fml/project-faq.fml at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/fml/project-faq.fml at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Frequently Asked Questions About Project Metadata</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="./css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Frequently Asked Questions About Project Metadata <a href="https://github.com/apache/maven-site/tree/master/content/fml/project-faq.fml"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="download.cgi" title="Download">Download</a></li>
@@ -136,13 +136,13 @@
           </div>
         </header>
         <main id="bodyColumn"  class="span10" >
-<section>
-<h1><a id="top">Frequently Asked Questions About Project Metadata</a></h1>
+<section><a id="top"></a>
+<h1>Frequently Asked Questions About Project Metadata</h1>
 <ol style="list-style-type: decimal">
 <li><a href="#why-care">Why do I care?</a></li>
 <li><a href="#how-to-improve-metadata">How do I make sure my project's dependency metadata is correct?</a></li></ol></section>
-<dl>
-<dt><a id="why-care">Why do I care?</a></dt>
+<dl><a id="why-care"></a>
+<dt>Why do I care?</dt>
 <dd>
         
 <p>
@@ -173,8 +173,8 @@
           leaves this responsibility to the users of your project.
        </p>
       
-<p><a href="#top">[top]</a></p><hr /></dd>
-<dt><a id="how-to-improve-metadata">How do I make sure my project's dependency metadata is correct?</a></dt>
+<p style="text-align: right;"><a href="#top">[top]</a></p><hr /></dd><a id="how-to-improve-metadata"></a>
+<dt>How do I make sure my project's dependency metadata is correct?</dt>
 <dd>
         
 <p>
@@ -233,7 +233,7 @@
           for more information.
        </p>
       
-<p><a href="#top">[top]</a></p></dd></dl>
+<p style="text-align: right;"><a href="#top">[top]</a></p></dd></dl>
         </main>
       </div>
     </div>

Modified: maven/website/content/project-info.html
==============================================================================
--- maven/website/content/project-info.html (original)
+++ maven/website/content/project-info.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from org.apache.maven.plugins:maven-site-plugin:4.0.0-M4:CategorySummaryDocumentRenderer at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from org.apache.maven.plugins:maven-site-plugin:4.0.0-M6:CategorySummaryDocumentRenderer at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Project Information</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="./css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Project Information</li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="download.cgi" title="Download">Download</a></li>

Modified: maven/website/content/project-roles.html
==============================================================================
--- maven/website/content/project-roles.html (original)
+++ maven/website/content/project-roles.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/project-roles.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/project-roles.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Apache Maven Project Roles</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="./css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Apache Maven Project Roles <a href="https://github.com/apache/maven-site/tree/master/content/markdown/project-roles.md"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="download.cgi" title="Download">Download</a></li>

Modified: maven/website/content/reference/maven-classloading.html
==============================================================================
--- maven/website/content/reference/maven-classloading.html (original)
+++ maven/website/content/reference/maven-classloading.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/reference/maven-classloading.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/reference/maven-classloading.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Maven classloading</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="../css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Maven classloading <a href="https://github.com/apache/maven-site/tree/master/content/markdown/reference/maven-classloading.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
@@ -154,7 +154,8 @@ under the License.
 <p>Core extension can use <code>META-INF/maven/extension.xml</code> descriptor to declare packages and artifacts exported by the extension. If the descriptor is not present, no packages or artifacts are exported, but the extension can still contribute components to Maven Core extension points.</p>
 <p>Core extensions are configured in <code>${maven.projectBasedir}/.mvn/extensions.xml</code> configuration file.</p>
 
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+<div class="verbatim">
+<pre><code class="language-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;extensions&gt;
   &lt;extension&gt;
     &lt;groupId&gt;...&lt;/groupId&gt;
@@ -189,7 +190,8 @@ under the License.
 <h2>Exported artifacts and packages</h2>
 <p>Maven Core, Session and Build Extensions use <code>META-INF/maven/extension.xml</code> descriptor to declare API packages and artifacts exported by the classloader.</p>
 
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+<div class="verbatim">
+<pre><code class="language-xml">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;extension&gt;
  &lt;!-- 
    | list of exported classname prefixes.

Modified: maven/website/content/release-notes-all.html
==============================================================================
--- maven/website/content/release-notes-all.html (original)
+++ maven/website/content/release-notes-all.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/release-notes-all.md.vm at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/release-notes-all.md.vm at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Release Notes</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="./css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Release Notes <a href="https://github.com/apache/maven-site/tree/master/content/markdown/release-notes-all.md.vm"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="download.cgi" title="Download">Download</a></li>

Modified: maven/website/content/repositories/artifacts.html
==============================================================================
--- maven/website/content/repositories/artifacts.html (original)
+++ maven/website/content/repositories/artifacts.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/artifacts.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/repositories/artifacts.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Maven Artifacts</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="../css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Maven Artifacts <a href="https://github.com/apache/maven-site/tree/master/content/markdown/repositories/artifacts.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
@@ -363,7 +363,8 @@ above may be extended by various plugins
 <code>org.project:reusable-test-support:1.0:tests:jar</code>. With type handlers above, maybe surprisingly, the dependency to
 this very same artifact can be described in two ways:</p>
 
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml">&lt;dependency&gt;
+<div class="verbatim">
+<pre><code class="language-xml">&lt;dependency&gt;
   &lt;groupId&gt;org.project&lt;/groupId&gt;
   &lt;artifactId&gt;reusable-test-support&lt;/artifactId&gt;
   &lt;version&gt;1.0&lt;/version&gt;
@@ -372,7 +373,8 @@ this very same artifact can be described
 </code></pre></div>
 <p>and the equivalent dependency would be:</p>
 
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml">&lt;dependency&gt;
+<div class="verbatim">
+<pre><code class="language-xml">&lt;dependency&gt;
   &lt;groupId&gt;org.project&lt;/groupId&gt;
   &lt;artifactId&gt;reusable-test-support&lt;/artifactId&gt;
   &lt;version&gt;1.0&lt;/version&gt;

Modified: maven/website/content/repositories/index.html
==============================================================================
--- maven/website/content/repositories/index.html (original)
+++ maven/website/content/repositories/index.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/index.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/repositories/index.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Maven Repositories</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="../css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Maven Repositories <a href="https://github.com/apache/maven-site/tree/master/content/markdown/repositories/index.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
@@ -155,7 +155,7 @@ fundamental concepts of Maven since its
 and developed since the beginning of Maven project itself.</p>
 
 <p>
-<img src="../repository/maven-repositories.png" alt="" />
+<img src="../repository/maven-repositories.png" usemap="#map" />
 <map name="map">
   <area shape="rect" coords="596,326,666,363" alt="JBoss" href="http://repository.jboss.org/maven2/" />
   <area shape="rect" coords="0,184,460,421" alt="central (default)" href="../repository/index.html" />

Modified: maven/website/content/repositories/layout.html
==============================================================================
--- maven/website/content/repositories/layout.html (original)
+++ maven/website/content/repositories/layout.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/layout.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/repositories/layout.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Maven Repository Layout</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="../css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Maven Repository Layout <a href="https://github.com/apache/maven-site/tree/master/content/markdown/repositories/layout.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
@@ -194,19 +194,23 @@ the files on file paths for consumption
 
 <p>And using these properties transformed as above, we can construct following path (if classifier not present):</p>
 
-<div class="source"><pre class="prettyprint linenums"><code>${groupId as directory}/${artifactId}/${baseVersion}/${artifactId}-${version}.${extension}
+<div class="verbatim">
+<pre><code>${groupId as directory}/${artifactId}/${baseVersion}/${artifactId}-${version}.${extension}
 </code></pre></div>
 <p>or if classifier present:</p>
 
-<div class="source"><pre class="prettyprint linenums"><code>${groupId as directory}/${artifactId}/${baseVersion}/${artifactId}-${version}-${classifier}.${extension}
+<div class="verbatim">
+<pre><code>${groupId as directory}/${artifactId}/${baseVersion}/${artifactId}-${version}-${classifier}.${extension}
 </code></pre></div>
 <p>So the example artifact above noted as GAV:</p>
 
-<div class="source"><pre class="prettyprint linenums"><code>org.apache.maven:apache-maven:3.8.4:bin:tar.gz
+<div class="verbatim">
+<pre><code>org.apache.maven:apache-maven:3.8.4:bin:tar.gz
 </code></pre></div>
 <p>is translated to path as:</p>
 
-<div class="source"><pre class="prettyprint linenums"><code>org/apache/maven/apache-maven/3.8.4/apache-maven-3.8.4-bin.tar.gz
+<div class="verbatim">
+<pre><code>org/apache/maven/apache-maven/3.8.4/apache-maven-3.8.4-bin.tar.gz
 </code></pre></div>
 <p>And that is it! By applying this &#x201c;algorithm&#x201d; above to ANY Artifact we can build up the path segment that
 artifact is expected to be.</p>

Modified: maven/website/content/repositories/local.html
==============================================================================
--- maven/website/content/repositories/local.html (original)
+++ maven/website/content/repositories/local.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/local.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/repositories/local.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Maven Local Repositories</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="../css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Maven Local Repositories <a href="https://github.com/apache/maven-site/tree/master/content/markdown/repositories/local.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>

Modified: maven/website/content/repositories/metadata.html
==============================================================================
--- maven/website/content/repositories/metadata.html (original)
+++ maven/website/content/repositories/metadata.html Fri Mar 24 11:57:50 2023
@@ -2,14 +2,14 @@
 
 
 <!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/metadata.md at 2023-03-24
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/markdown/repositories/metadata.md at 2023-03-24
  | Rendered using Apache Maven Fluido Skin 1.11.1
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
-    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
+    <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M6" />
     <title>Maven &#x2013; Maven Metadata</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
     <link rel="stylesheet" href="../css/site.css" />
@@ -47,7 +47,7 @@
       <li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
       <li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Maven Metadata <a href="https://github.com/apache/maven-site/tree/master/content/markdown/repositories/metadata.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
-        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-03-24</li>
+        <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2022-12-11</li>
         <li class="pull-right"><span class="divider">|</span>
 <a href="../scm.html" title="Get Sources">Get Sources</a></li>
         <li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>