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/31 16:05:32 UTC

svn commit: r1908871 [7/14] - in /maven/website/content: ./ apache-resource-bundles/ archives/maven-2.x/ background/ css/ developers/ developers/conventions/ developers/release/ developers/website/ docs/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2...

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 Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-dependency-mechanism.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -16,18 +16,18 @@
     <meta name="date" content="2005-10-12
 2016-06-17" />
     <title>Maven &#x2013; Introduction to the Dependency Mechanism</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -49,8 +49,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to the Dependency Mechanism <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -210,7 +210,7 @@
 <li><b>system</b><br />This scope is similar to <code>provided</code> except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository.</li>
 <li><b>import</b><br />This scope is only supported on a dependency of type <code>pom</code> in the <code>&lt;dependencyManagement&gt;</code> section. It indicates the dependency is to be replaced with the effective list of dependencies in the specified POM's <code>&lt;dependencyManagement&gt;</code> section. Since they are replaced, dependencies with a scope of <code>import</code> do not actually participate in limiting the transitivity of a dependency.</li></ul>
 <p>Each of the scopes (except for <code>import</code>) affects transitive dependencies in different ways, as is demonstrated in the table below. If a dependency is set to the scope in the left column, a transitive dependency of that dependency with the scope across the top row results in a dependency in the main project with the scope listed at the intersection. If no scope is listed, it means the dependency is omitted.</p>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <td style="text-align: left;"></td>
 <td style="text-align: left;">compile</td>
@@ -245,8 +245,7 @@
 <h2><a id="Dependency_Management">Dependency Management</a></h2>
 <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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -272,8 +271,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>Project B:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -295,8 +293,7 @@
 &lt;/project&gt;
 </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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencyManagement&gt;
@@ -335,8 +332,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>Then the two child POMs become much simpler:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -354,8 +350,7 @@
   &lt;/dependencies&gt;
 &lt;/project&gt;
 </pre></div>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -378,8 +373,7 @@
 <p><b>NOTE:</b> In two of these dependency references, we had to specify the &lt;type/&gt; element. This is because the minimal set of information for matching a dependency reference against a dependencyManagement section is actually <b>{groupId, artifactId, type, classifier}</b>. In many cases, these dependencies will refer to jar artifacts with no classifier. This allows us to shorthand the identity set to <b>{groupId, artifactId}</b>, since the default for the type field is <code>jar</code>, and the default classifier is null.</p>
 <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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
  &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
  &lt;groupId&gt;maven&lt;/groupId&gt;
@@ -416,8 +410,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>Project B:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   &lt;parent&gt;
     &lt;artifactId&gt;A&lt;/artifactId&gt;
@@ -465,8 +458,7 @@
 <h3><a id="Importing_Dependencies">Importing Dependencies</a></h3>
 <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 &quot;import&quot;.</p>
 <p>Project B:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;groupId&gt;maven&lt;/groupId&gt;
@@ -509,8 +501,7 @@
 </pre></div>
 <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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
  &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
  &lt;groupId&gt;maven&lt;/groupId&gt;
@@ -537,8 +528,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>Project Y:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
  &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
  &lt;groupId&gt;maven&lt;/groupId&gt;
@@ -565,8 +555,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>Project Z:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;groupId&gt;maven&lt;/groupId&gt;
@@ -600,8 +589,7 @@
 <h3><a id="Bill_of_Materials_.28BOM.29_POMs">Bill of Materials (BOM) POMs</a></h3>
 <p>Imports are most effective when used for defining a &quot;library&quot; 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 &quot;bill of materials&quot; (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="verbatim source">
-<pre>
+<div class="verbatim 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;
     xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
@@ -635,8 +623,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>The parent subproject has the BOM POM as its parent. It is a normal multiproject pom.</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim 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;
      xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
@@ -672,8 +659,7 @@
 &lt;/project&gt;
 </pre></div>
 <p>Next are the actual project POMs.</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim 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;
      xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
@@ -717,8 +703,7 @@
 &lt;/project&gt;
 </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="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;
+<div class="verbatim 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;
      xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;groupId&gt;com.test&lt;/groupId&gt;
@@ -758,8 +743,7 @@
 <p><code>Important note: This is deprecated.</code></p>
 <p>Dependencies with the scope <i>system</i> 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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -775,8 +759,7 @@
 &lt;/project&gt;
 </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="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;dependencies&gt;
     &lt;dependency&gt;

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 Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="Allan Ramirez" />
     <meta name="date" content="2006-01-23" />
     <title>Maven &#x2013; Optional Dependencies and Dependency Exclusions</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Optional Dependencies and Dependency Exclusions <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -158,8 +158,7 @@
 <p>Optional dependencies save space and memory. They prevent problematic jars that violate a license agreement or cause classpath issues from being bundled into a WAR, EAR, fat jar, or the like. </p></section><section>
 <h3>How do I use the optional tag?</h3>
 <p>A dependency is declared optional by setting the <code>&lt;optional&gt;</code> element to true in its dependency declaration:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -191,8 +190,7 @@ Project-X -&gt; Project-A
 <p>Since Maven resolves dependencies transitively, it is possible for unwanted dependencies to be included in your project's classpath. For example, a certain older jar may have security issues or be incompatible with the Java version you're using. To address this, Maven allows you to exclude specific dependencies. Exclusions are set on a specific dependency in your POM, and are targeted at a specific groupId and artifactId. When you build your project, that artifact will not be added to your project's classpath <i>by way of the dependency in which the exclusion was declared</i>.</p><section>
 <h3>How to use dependency exclusions</h3>
 <p>Add an <code>&lt;exclusions&gt;</code> element in the <code>&lt;dependency&gt;</code> element by which the problematic jar is included.</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;dependencies&gt;
@@ -225,16 +223,14 @@ Project-A
 <div class="verbatim">
 <pre>B, C, D, E, F</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>&lt;optional&gt;true&lt;/optional&gt;</code>:</p>
-<div class="verbatim source">
-<pre>&lt;dependency&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;dependency&gt;
   &lt;groupId&gt;sample.ProjectD&lt;/groupId&gt;
   &lt;artifactId&gt;ProjectD&lt;/artifactId&gt;
   &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
   &lt;optional&gt;true&lt;/optional&gt;
 &lt;/dependency&gt;</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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;groupId&gt;sample.ProjectA&lt;/groupId&gt;
@@ -283,8 +279,7 @@ Project-A
    -&gt; Project C
 </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="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;groupId&gt;sample.ProjectA&lt;/groupId&gt;

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 Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="John Casey" />
     <meta name="date" content="2009-08-01" />
     <title>Maven &#x2013; Introduction to Plugin Prefix Resolution</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to Plugin Prefix Resolution <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -152,8 +152,7 @@
 <li><code>maven-${prefix}-plugin</code> - for official plugins maintained by the Apache Maven team itself (you <b>must not</b> use this naming pattern for your plugin, see <a href="../plugin/guide-java-plugin-development.html#Plugin_Naming_Convention_and_Apache_Maven_Trademark">this note for more informations</a>)</li>
 <li><code>${prefix}-maven-plugin</code> - for plugins from other sources</li></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="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;build&gt;
     ...
@@ -183,8 +182,7 @@
 <h2>Configuring Maven to Search for Plugins</h2>
 <p>By default, Maven will search the groupId <b>org.apache.maven.plugins</b> 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 <b>pluginGroups</b> section, listing the plugin groupIds you want to search (each groupId goes in its own <b>pluginGroup</b> sub-element). For example, if my project uses a Modello model file, I might have the following in my settings:</p>
-<div class="verbatim source">
-<pre>&lt;pluginGroups&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;pluginGroups&gt;
   &lt;pluginGroup&gt;org.codehaus.modello&lt;/pluginGroup&gt;
 &lt;/pluginGroups&gt;</pre></div>
 <p>This allows me to execute the following, which will generate Java classes from the model:</p>

Modified: maven/website/content/guides/introduction/introduction-to-plugins.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-plugins.html (original)
+++ maven/website/content/guides/introduction/introduction-to-plugins.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-plugins.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="John Casey" />
     <meta name="date" content="2005-06-24" />
     <title>Maven &#x2013; Introduction to Maven Plugin Development</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to Maven Plugin Development <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-plugins.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>

Modified: maven/website/content/guides/introduction/introduction-to-profiles.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-profiles.html (original)
+++ maven/website/content/guides/introduction/introduction-to-profiles.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-profiles.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="John Casey/Allan Ramirez" />
     <meta name="date" content="2008-01-01" />
     <title>Maven &#x2013; Introduction to build profiles</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to build profiles <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-profiles.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -202,8 +202,7 @@
 <div class="verbatim">
 <pre>mvn groupId:artifactId:goal -P profile-1,profile-2,?profile-3</pre></div>
 <p>Profiles can be activated in the Maven settings, via the <code>&lt;activeProfiles&gt;</code> section. This section takes a list of <code>&lt;activeProfile&gt;</code> elements, each containing a profile-id inside.</p>
-<div class="verbatim source">
-<pre>&lt;settings&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;settings&gt;
   ...
   &lt;activeProfiles&gt;
     &lt;activeProfile&gt;profile-1&lt;/activeProfile&gt;
@@ -215,8 +214,7 @@
 <p>Profiles can be automatically triggered based on the detected state of the build environment. These triggers are specified via an <code>&lt;activation&gt;</code> section in the profile itself. Currently, this detection is limited to JDK version matching, operating system matching or the presence/the value of a system property. Here are some examples.</p><section>
 <h5>JDK</h5>
 <p>The following configuration will trigger the profile when the JDK's version <i>starts with</i> &quot;1.4&quot; (eg. &quot;1.4.0_08&quot;, &quot;1.4.2_07&quot;, &quot;1.4&quot;), in particular it <i>won't be active</i> for <b>newer</b> versions like &quot;1.8&quot; or &quot;11&quot;:</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;jdk&gt;1.4&lt;/jdk&gt;
@@ -225,8 +223,7 @@
   &lt;/profile&gt;
 &lt;/profiles&gt;</pre></div>
 <p>Ranges can also be used as of Maven 2.1 (refer to the <a href="/enforcer/enforcer-rules/versionRanges.html"> Enforcer Version Range Syntax</a> for more information). Range values must start with either <code>[</code> or <code>(</code> otherwise the value is interpreted as prefix. The following honours versions 1.3, 1.4 and 1.5.</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;jdk&gt;[1.3,1.6)&lt;/jdk&gt;
@@ -237,8 +234,7 @@
 <p><i>Note:</i> an upper bound such as <code>,1.5]</code> is likely not to include most releases of 1.5, since they will have an additional &quot;patch&quot; release such as <code>_05</code> that is not taken into consideration in the above range.</p></section><section>
 <h5>OS</h5>
 <p>This next one will activate based on the detected operating system. See the <a href="/enforcer/enforcer-rules/requireOS.html">Maven Enforcer Plugin</a> for more details about OS values.</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;os&gt;
@@ -253,8 +249,7 @@
 &lt;/profiles&gt;</pre></div></section><section>
 <h5>Property</h5>
 <p>The profile below will be activated when the system property &quot;debug&quot; is specified with any value:</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;property&gt;
@@ -265,8 +260,7 @@
   &lt;/profile&gt;
 &lt;/profiles&gt;</pre></div>
 <p>The following profile will be activated when the system property &quot;debug&quot; is not defined at all:</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;property&gt;
@@ -277,8 +271,7 @@
   &lt;/profile&gt;
 &lt;/profiles&gt;</pre></div>
 <p>The following profile will be activated when the system property &quot;debug&quot; is not defined, or is defined with a value which is not &quot;true&quot;.</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;property&gt;
@@ -294,8 +287,7 @@
 <pre>mvn groupId:artifactId:goal
 mvn groupId:artifactId:goal -Ddebug=false</pre></div>
 <p>The next example will trigger the profile when the system property &quot;environment&quot; is specified with the value &quot;test&quot;:</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;property&gt;
@@ -312,8 +304,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
 <p>As of Maven 3.0, profiles in the POM can also be activated based on properties from active profiles from the <code>settings.xml</code>.</p>
 <p><b>Note</b>: Environment variables like <code>FOO</code> are available as properties of the form <code>env.FOO</code>. Further note that environment variable names are normalized to all upper-case on Windows.</p>
 <p>Since Maven 3.9.0 one can also evaluate the POM's packaging value by referencing property <code>packaging</code>. This is only useful where the profile activation is defined in a common parent POM which is reused among multiple Maven projects. The next example will trigger the profile when a project with packaging <code>war</code> is built:</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;property&gt;
@@ -326,8 +317,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
 &lt;/profiles&gt;</pre></div></section><section>
 <h5>Files</h5>
 <p>This example will trigger the profile when the generated file <code>target/generated-sources/axistools/wsdl2java/org/apache/maven</code> is missing.</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;activation&gt;
       &lt;file&gt;
@@ -339,8 +329,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
 &lt;/profiles&gt;</pre></div>
 <p>As of Maven 2.0.9, the tags <code>&lt;exists&gt;</code> and <code>&lt;missing&gt;</code> could be interpolated. Supported variables are system properties like <code>${user.home}</code> and environment variables like <code>${env.HOME}</code>. Please note that properties and values defined in the POM itself are not available for interpolation here, e.g. the above example activator cannot use <code>${project.build.directory}</code> but needs to hard-code the path <code>target</code>.</p>
 <p>Profiles can also be active by default using a configuration like the following:</p>
-<div class="verbatim source">
-<pre>&lt;profiles&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;profiles&gt;
   &lt;profile&gt;
     &lt;id&gt;profile-1&lt;/id&gt;
     &lt;activation&gt;
@@ -394,8 +383,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
 <h2>Profile Order</h2>
 <p>All profile elements in a POM from active profiles overwrite the global elements with the same name of the POM or extend those in case of collections. In case multiple profiles are active in the same POM or external file, the ones which are defined <b>later</b> take precedence over the ones defined <b>earlier</b> (independent of their profile id and activation order).</p>
 <p>Example:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;repositories&gt;
     &lt;repository&gt;
@@ -439,8 +427,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
 <p>There are two main problem areas to keep in mind when using profiles. First are external properties, usually used in plugin configurations. These pose the risk of breaking portability in your project. The other, more subtle area is the incomplete specification of a natural set of profiles.</p><section>
 <h3>External Properties</h3>
 <p>External property definition concerns any property value defined outside the <code>pom.xml</code> but not defined in a corresponding profile inside it. The most obvious usage of properties in the POM is in plugin configuration. While it is certainly possible to break project portability without properties, these critters can have subtle effects that cause builds to fail. For example, specifying appserver paths in a profile that is specified in the <code>settings.xml</code> may cause your integration test plugin to fail when another user on the team attempts to build without a similar <code>settings.xml</code>. Consider the following <code>pom.xml</code> snippet for a web application project:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;build&gt;
     &lt;plugins&gt;
@@ -458,8 +445,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
   ...
 &lt;/project&gt;</pre></div>
 <p>Now, in your local <code>${user.home}/.m2/settings.xml</code>, you have:</p>
-<div class="verbatim source">
-<pre>&lt;settings&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;settings&gt;
   ...
   &lt;profiles&gt;
     &lt;profile&gt;
@@ -481,8 +467,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
 <p>Another, less attractive answer might be standardization of development environments. However, this will tend to compromise the productivity gain that Maven is capable of providing.</p></section><section>
 <h3>Incomplete Specification of a Natural Profile Set</h3>
 <p>In addition to the above portability-breaker, it's easy to fail to cover all cases with your profiles. When you do this, you're usually leaving one of your target environments high and dry. Let's take the example <code>pom.xml</code> snippet from above one more time:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;build&gt;
     &lt;plugins&gt;
@@ -500,8 +485,7 @@ mvn groupId:artifactId:goal -Ddebug=fals
   ...
 &lt;/project&gt;</pre></div>
 <p>Now, consider the following profile, which would be specified inline in the <code>pom.xml</code>:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;profiles&gt;
     &lt;profile&gt;

Modified: maven/website/content/guides/introduction/introduction-to-repositories.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-repositories.html (original)
+++ maven/website/content/guides/introduction/introduction-to-repositories.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-repositories.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -14,18 +14,18 @@
     <meta name="author" content="Brian Fox" />
     <meta name="date" content="2008-05-13" />
     <title>Maven &#x2013; Introduction to Repositories</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -47,8 +47,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to Repositories <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-repositories.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -192,8 +192,7 @@
 <p>It should be noted that Maven intends to include enhanced support for such features in the future, including click through licenses on downloading, and verification of signatures.</p></section><section>
 <h2>Using the Internal Repository</h2>
 <p>Using the internal repository is quite simple. Simply make a change to add a <code>repositories</code> element:</p>
-<div class="verbatim source">
-<pre>
+<div class="verbatim source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
   &lt;repositories&gt;

Modified: maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-lifecycle.html (original)
+++ maven/website/content/guides/introduction/introduction-to-the-lifecycle.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-the-lifecycle.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -14,18 +14,18 @@
     <meta name="date" content="2006-06-16
 2015-04-04" />
     <title>Maven &#x2013; Introduction to the Build Lifecycle</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -47,8 +47,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to the Build Lifecycle <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-the-lifecycle.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -205,7 +205,7 @@
 <h3><a id="Packaging">Packaging</a></h3>
 <p>The first, and most common way, is to set the packaging for your project via the equally named POM element <code>&lt;packaging&gt;</code>. Some of the valid packaging values are <code>jar</code>, <code>war</code>, <code>ear</code> and <code>pom</code>. If no packaging value has been specified, it will default to <code>jar</code>.</p>
 <p>Each packaging contains a list of goals to bind to a particular phase. For example, the <code>jar</code> packaging will bind the following goals to build phases of the default lifecycle.</p>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>
@@ -241,8 +241,7 @@
 <p>As you will see in the later sections, plugins can contain information that indicates which lifecycle phase to bind a goal to. Note that adding the plugin on its own is not enough information - you must also specify the goals you want to run as part of your build.</p>
 <p>The goals that are configured will be added to the goals already bound to the lifecycle from the packaging selected. If more than one goal is bound to a particular phase, the order used is that those from the packaging are executed first, followed by those configured in the POM. Note that you can use the <code>&lt;executions&gt;</code> element to gain more control over the order of particular goals.</p>
 <p>For example, the Modello plugin binds by default its goal <code>modello:java</code> to the <code>generate-sources</code> phase (Note: The <code>modello:java</code> goal generates Java source codes). So to use the Modello plugin and have it generate sources from a model and incorporate that into the build, you would add the following to your POM in the <code>&lt;plugins&gt;</code> section of <code>&lt;build&gt;</code>:</p>
-<div class="verbatim source">
-<pre> &lt;plugin&gt;
+<div class="verbatim source"><pre class="prettyprint linenums"> &lt;plugin&gt;
    &lt;groupId&gt;org.codehaus.modello&lt;/groupId&gt;
    &lt;artifactId&gt;modello-maven-plugin&lt;/artifactId&gt;
    &lt;version&gt;1.8.1&lt;/version&gt;
@@ -263,8 +262,7 @@
 <p>You might be wondering why that <code>&lt;executions&gt;</code> element is there. That is so that you can run the same goal multiple times with different configuration if needed. Separate executions can also be given an ID so that during inheritance or the application of profiles you can control whether goal configuration is merged or turned into an additional execution.</p>
 <p>When multiple executions are given that match a particular phase, they are executed in the order specified in the POM, with inherited executions running first.</p>
 <p>Now, in the case of <code>modello:java</code>, it only makes sense in the <code>generate-sources</code> phase. But some goals can be used in more than one phase, and there may not be a sensible default. For those, you can specify the phase yourself. For example, let's say you have a goal <code>display:time</code> that echos the current time to the commandline, and you want it to run in the <code>process-test-resources</code> phase to indicate when the tests were started. This would be configured like so:</p>
-<div class="verbatim source">
-<pre> &lt;plugin&gt;
+<div class="verbatim source"><pre class="prettyprint linenums"> &lt;plugin&gt;
    &lt;groupId&gt;com.mycompany.example&lt;/groupId&gt;
    &lt;artifactId&gt;display-maven-plugin&lt;/artifactId&gt;
    &lt;version&gt;1.0&lt;/version&gt;
@@ -281,7 +279,7 @@
 <h2><a id="Lifecycle_Reference">Lifecycle Reference</a></h2>
 <p>The following lists all build phases of the <code>default</code>, <code>clean</code> and <code>site</code> lifecycles, which are executed in the order given up to the point of the one specified.</p><section>
 <h3>Clean Lifecycle</h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>Description</th></tr>
@@ -295,7 +293,7 @@
 <td style="text-align: left;"><code>post-clean</code></td>
 <td style="text-align: left;">execute processes needed to finalize the project cleaning</td></tr></table></section><section>
 <h3>Default Lifecycle</h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>Description</th></tr>
@@ -369,7 +367,7 @@
 <td style="text-align: left;"><code>deploy</code></td>
 <td style="text-align: left;">done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.</td></tr></table></section><section>
 <h3>Site Lifecycle</h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>Description</th></tr>
@@ -389,7 +387,7 @@
 <h2><a id="Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></h2>
 <p>Some phases have goals bound to them by default. And for the default lifecycle, these bindings depend on the packaging value. Here are some of the goal-to-build-phase bindings.</p><section>
 <h3>Clean Lifecycle Bindings</h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>
@@ -397,7 +395,7 @@
 <td style="text-align: left;"><code>clean</code></td>
 <td style="text-align: left;"><code>clean:clean</code></td></tr></table></section><section>
 <h3>Default Lifecycle Bindings - Packaging <code>ejb</code> / <code>ejb3</code> / <code>jar</code> / <code>par</code> / <code>rar</code> / <code>war</code></h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>
@@ -426,7 +424,7 @@
 <td style="text-align: left;"><code>deploy</code></td>
 <td style="text-align: left;"><code>deploy:deploy</code></td></tr></table></section><section>
 <h3>Default Lifecycle Bindings - Packaging <code>ear</code></h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>
@@ -446,7 +444,7 @@
 <td style="text-align: left;"><code>deploy</code></td>
 <td style="text-align: left;"><code>deploy:deploy</code></td></tr></table></section><section>
 <h3>Default Lifecycle Bindings - Packaging <code>maven-plugin</code></h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>
@@ -478,7 +476,7 @@
 <td style="text-align: left;"><code>deploy</code></td>
 <td style="text-align: left;"><code>deploy:deploy</code></td></tr></table></section><section>
 <h3>Default Lifecycle Bindings - Packaging <code>pom</code></h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>
@@ -492,7 +490,7 @@
 <td style="text-align: left;"><code>deploy</code></td>
 <td style="text-align: left;"><code>deploy:deploy</code></td></tr></table></section><section>
 <h3>Site Lifecycle Bindings</h3>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <th>Phase</th>
 <th>plugin:goal</th></tr>

Modified: maven/website/content/guides/introduction/introduction-to-the-pom.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-pom.html (original)
+++ maven/website/content/guides/introduction/introduction-to-the-pom.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-the-pom.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -15,18 +15,18 @@
     <meta name="author" content="Brett Porter" />
     <meta name="date" content="2009-02-04" />
     <title>Maven &#x2013; Introduction to the POM</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -48,8 +48,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to the POM <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-the-pom.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -184,8 +184,7 @@
 <li><code>artifactId</code> - the id of the artifact (project)</li>
 <li><code>version</code> - the version of the artifact under the specified group</li></ul>
 <p>Here's an example:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -209,8 +208,7 @@
 <h3><a id="Example_1">Example 1</a></h3><section>
 <h4>The Scenario</h4>
 <p>As an example, let us reuse our previous artifact, com.mycompany.app:my-app:1. And let us introduce another artifact, com.mycompany.app:my-module:1.</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -227,8 +225,7 @@
 <h4>The Solution</h4>
 <p>Now, if we were to turn com.mycompany.app:my-app:1 into a parent artifact of com.mycompany.app:my-module:1,we will have to modify com.mycompany.app:my-module:1's POM to the following configuration:</p>
 <p><b>com.mycompany.app:my-module:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;parent&gt;
@@ -243,8 +240,7 @@
 &lt;/project&gt;</pre></div>
 <p>Notice that we now have an added section, the parent section. This section allows us to specify which artifact is the parent of our POM. And we do so by specifying the fully qualified artifact name of the parent POM. With this setup, our module can now inherit some of the properties of our parent POM.</p>
 <p>Alternatively, if you want the groupId or the version of your modules to be the same as their parents, you can remove the groupId or the version identity of your module in its POM.</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;parent&gt;
@@ -269,8 +265,7 @@
      `-- pom.xml</pre></div></section><section>
 <h4>The Solution</h4>
 <p>To address this directory structure (or any other directory structure), we would have to add the <code>&lt;relativePath&gt;</code> element to our parent section.</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;parent&gt;
@@ -293,8 +288,7 @@
 <h4>The Scenario</h4>
 <p>Given the previous original artifact POMs and directory structure:</p>
 <p><b>com.mycompany.app:my-app:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -302,8 +296,7 @@
   &lt;version&gt;1&lt;/version&gt;
 &lt;/project&gt;</pre></div>
 <p><b>com.mycompany.app:my-module:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -318,8 +311,7 @@
  `-- pom.xml</pre></div></section><section>
 <h4>The Solution</h4>
 <p>If we are to aggregate my-module into my-app, we would only have to modify my-app.</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -346,8 +338,7 @@
 <p>How would the parent POM specify its modules?</p></section><section>
 <h4>The Solution</h4>
 <p>The answer? - the same way as Example 3, by specifying the path to the module.</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -372,8 +363,7 @@
 <h4>The Scenario</h4>
 <p>Given the previous original artifact POMs again,</p>
 <p><b>com.mycompany.app:my-app:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -381,8 +371,7 @@
   &lt;version&gt;1&lt;/version&gt;
 &lt;/project&gt;</pre></div>
 <p><b>com.mycompany.app:my-module:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -399,8 +388,7 @@
 <h4>The Solution</h4>
 <p>To do both project inheritance and aggregation, you only have to apply all three rules.</p>
 <p><b>com.mycompany.app:my-app:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -413,8 +401,7 @@
   &lt;/modules&gt;
 &lt;/project&gt;</pre></div>
 <p><b>com.mycompany.app:my-module:1's POM</b></p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 
   &lt;parent&gt;
@@ -431,15 +418,14 @@
 <h2><a id="Project_Interpolation">Project Interpolation</a> and Variables</h2>
 <p>One of the practices that Maven encourages is <i>don't repeat yourself</i>. However, there are circumstances where you will need to use the same value in several different locations. To assist in ensuring the value is only specified once, Maven allows you to use both your own and pre-defined variables in the POM.</p>
 <p>For example, to access the <code>project.version</code> variable, you would reference it like so:</p>
-<div class="verbatim source">
-<pre>  &lt;version&gt;${project.version}&lt;/version&gt;</pre></div>
+<div class="verbatim source"><pre class="prettyprint linenums">  &lt;version&gt;${project.version}&lt;/version&gt;</pre></div>
 <p>One factor to note is that these variables are processed <i>after</i> inheritance as outlined above. This means that if a parent project uses a variable, then its definition in the child, not the parent, will be the one eventually used.</p><section>
 <h3><a id="Available_Variables">Available Variables</a></h3><section>
 <h4>Project Model Variables</h4>
 <p>Any field of the model that is a single value element can be referenced as a variable. For example, <code>${project.groupId}</code>, <code>${project.version}</code>, <code>${project.build.sourceDirectory}</code> and so on. Refer to the POM reference to see a full list of properties.</p>
 <p>These variables are all referenced by the prefix &quot;<code>project.</code>&quot;. You may also see references with <code>pom.</code> as the prefix, or the prefix omitted entirely - these forms are now deprecated and should not be used.</p></section><section>
 <h4>Special Variables</h4>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <td style="text-align: left;"><code>project.basedir</code></td>
 <td style="text-align: left;">The directory that the current project resides in.</td></tr>
@@ -450,8 +436,7 @@
 <td style="text-align: left;"><code>maven.build.timestamp</code></td>
 <td style="text-align: left;">The timestamp that denotes the start of the build (UTC). <i>Since Maven 2.1.0-M1</i></td></tr></table>
 <p>The format of the build timestamp can be customized by declaring the property <code>maven.build.timestamp.format</code> as shown in the example below:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;properties&gt;
     &lt;maven.build.timestamp.format&gt;yyyy-MM-dd'T'HH:mm:ss'Z'&lt;/maven.build.timestamp.format&gt;
@@ -461,8 +446,7 @@
 <p>The format pattern has to comply with the rules given in the API documentation for <a class="externalLink" href="https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html">SimpleDateFormat</a>. If the property is not present, the format defaults to the value already given in the example.</p></section><section>
 <h4>Properties</h4>
 <p>You are also able to reference any properties defined in the project as a variable. Consider the following example:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;properties&gt;
     &lt;mavenVersion&gt;3.0&lt;/mavenVersion&gt;

Modified: maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html (original)
+++ maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/introduction/introduction-to-the-standard-directory-layout.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="Jason van Zyl" />
     <meta name="date" content="2014-03-09" />
     <title>Maven &#x2013; Introduction to the Standard Directory Layout</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Introduction to the Standard Directory Layout <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/introduction/introduction-to-the-standard-directory-layout.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -149,7 +149,7 @@
 <h1>Introduction to the Standard Directory Layout</h1>
 <p>Having a common directory layout allows users familiar with one Maven project to immediately feel at home in another Maven project. The advantages are analogous to adopting a site-wide look-and-feel.</p>
 <p>The next section documents the directory layout expected by Maven and the directory layout created by Maven. Try to conform to this structure as much as possible. However, if you can't, these settings can be overridden via the project descriptor.</p>
-<table class="bodyTable bodyTableBorder">
+<table class="table table-bordered table-striped">
 <tr class="a">
 <td style="text-align: left;"><code>src/main/java</code></td>
 <td style="text-align: left;">Application/Library sources</td></tr>

Modified: maven/website/content/guides/mini/guide-3rd-party-jars-local.html
==============================================================================
--- maven/website/content/guides/mini/guide-3rd-party-jars-local.html (original)
+++ maven/website/content/guides/mini/guide-3rd-party-jars-local.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/mini/guide-3rd-party-jars-local.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -14,18 +14,18 @@
     <meta name="author" content="Robert Scholte" />
     <meta name="date" content="2013-07-13" />
     <title>Maven &#x2013; Guide to installing 3rd party JARs</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -47,8 +47,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Guide to installing 3rd party JARs <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/mini/guide-3rd-party-jars-local.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>

Modified: maven/website/content/guides/mini/guide-3rd-party-jars-remote.html
==============================================================================
--- maven/website/content/guides/mini/guide-3rd-party-jars-remote.html (original)
+++ maven/website/content/guides/mini/guide-3rd-party-jars-remote.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/mini/guide-3rd-party-jars-remote.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="Allan Ramirez" />
     <meta name="date" content="2006-02-22" />
     <title>Maven &#x2013; Guide to deploying 3rd party JARs to remote repository</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Guide to deploying 3rd party JARs to remote repository <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/mini/guide-3rd-party-jars-remote.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>

Modified: maven/website/content/guides/mini/guide-archive-configuration.html
==============================================================================
--- maven/website/content/guides/mini/guide-archive-configuration.html (original)
+++ maven/website/content/guides/mini/guide-archive-configuration.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/mini/guide-archive-configuration.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="Brett Porter" />
     <meta name="date" content="2006-06-21" />
     <title>Maven &#x2013; Guide to Configuring Archive Plugins</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Guide to Configuring Archive Plugins <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/mini/guide-archive-configuration.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -160,8 +160,7 @@
 <h2>Disabling Maven Meta Information</h2>
 <p>By default, Maven generated archives include the <code>META-INF/maven</code> directory, which contains the <code>pom.xml</code> file used to build the archive, and a <code>pom.properties</code> file that includes some basic properties in a small, easier to read format.</p>
 <p>To disable the generation of these files, include the following configuration for your plugin (in this example, the WAR plugin is used):</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;build&gt;
     &lt;plugins&gt;

Modified: maven/website/content/guides/mini/guide-assemblies.html
==============================================================================
--- maven/website/content/guides/mini/guide-assemblies.html (original)
+++ maven/website/content/guides/mini/guide-assemblies.html Fri Mar 31 16:05:29 2023
@@ -3,9 +3,9 @@
 
 <!--
  | Generated by Apache Maven Doxia Site Renderer 2.0.0-M6 from content/apt/guides/mini/guide-assemblies.apt at 2023-03-31
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Rendered using Apache Maven Fluido Skin 2.0.0-M5
 -->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
@@ -13,18 +13,18 @@
     <meta name="author" content="Jason van Zyl" />
     <meta name="date" content="2005-10-12" />
     <title>Maven &#x2013; Guide to Creating Assemblies</title>
-    <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
+    <link rel="stylesheet" href="../../css/apache-maven-fluido-2.0.0-M5.min.css" />
     <link rel="stylesheet" href="../../css/site.css" />
     <link rel="stylesheet" href="../../css/print.css" media="print" />
-    <script src="../../js/apache-maven-fluido-1.11.1.min.js"></script>
+    <script src="../../js/apache-maven-fluido-2.0.0-M5.min.js"></script>
 
     <!-- Matomo -->
     <script>
         var _paq = window._paq = window._paq || [];
-                _paq.push(['disableCookies']);
-                    _paq.push(['trackPageView']);
-                    _paq.push(['enableLinkTracking']);
-        
+        _paq.push(['disableCookies']);
+        _paq.push(['trackPageView']);
+        _paq.push(['enableLinkTracking']);
+
         (function() {
             var u="https://analytics.apache.org/";
             _paq.push(['setTrackerUrl', u+'/matomo.php']);
@@ -46,8 +46,8 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-      <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><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
+      <li><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
     <li class="active ">Guide to Creating Assemblies <a href="https://github.com/apache/maven-site/tree/master/content/apt/guides/mini/guide-assemblies.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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>
@@ -157,8 +157,7 @@
 <section>
 <h1>Guide to creating assemblies</h1>
 <p>The assembly mechanism in Maven provides an easy way to create distributions using a assembly descriptor and dependency information found in you POM. In order to use the assembly plug-in you need to configure the assembly plug-in in your POM and it might look like the following:</p>
-<div class="verbatim source">
-<pre>&lt;project&gt;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;parent&gt;
     &lt;artifactId&gt;maven&lt;/artifactId&gt;
     &lt;groupId&gt;org.apache.maven&lt;/groupId&gt;
@@ -196,8 +195,7 @@
 <p>You'll notice that the assembly descriptor is located in <code>${project.basedir}/src/assembly</code> which is the <a href="../introduction/introduction-to-the-standard-directory-layout.html">standard</a> location for assembly descriptors.</p><section>
 <h2>Creating a binary assembly</h2>
 <p>This is the most typical usage of the assembly plugin where you are creating a distribution for standard use.</p>
-<div class="verbatim source">
-<pre>&lt;assembly xmlns=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;assembly xmlns=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd&quot;&gt;
   &lt;id&gt;bin&lt;/id&gt;
   &lt;formats&gt;
@@ -230,8 +228,7 @@
 &lt;/assembly&gt;</pre></div>
 <p>You can use a manually defined assembly descriptor as mentioned before but it is simpler to use the <a href="/plugins/maven-assembly-plugin/descriptor-refs.html#bin">pre-defined assembly descriptor bin</a> in such cases.</p>
 <p>How to use such pre-defined assembly descriptors is described in the <a href="/plugins/maven-assembly-plugin/usage.html#Configuration">documentation of maven-assembly-plugin</a>.</p>
-<div class="verbatim source">
-<pre>&lt;assembly 
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;assembly 
   xmlns=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 
   http://maven.apache.org/xsd/assembly-1.1.2.xsd&quot;&gt;
@@ -267,8 +264,7 @@
 &lt;/assembly&gt;
 </pre></div>
 <p>If you like to create a source distribution package the best solution is to use the <a href="/plugins/maven-assembly-plugin/descriptor-refs.html#src">pre-defined assembly descriptor src</a> for such purposes.</p>
-<div class="verbatim source">
-<pre>&lt;assembly xmlns=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+<div class="verbatim source"><pre class="prettyprint linenums">&lt;assembly xmlns=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
   xsi:schemaLocation=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd&quot;&gt;
   &lt;id&gt;src&lt;/id&gt;
   &lt;formats&gt;