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 2019/06/09 13:59:37 UTC

svn commit: r1860906 [11/22] - 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/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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/introduction/introduction-to-the-lifecycle.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/introduction/introduction-to-the-lifecycle.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -143,9 +143,8 @@
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
-<h2><a name="Introduction_to_the_Build_Lifecycle"></a>Introduction to the Build Lifecycle</h2>
-<div class="section">
+<section>
+<h2><a name="Introduction_to_the_Build_Lifecycle"></a>Introduction to the Build Lifecycle</h2><section>
 <h3><a name="Table_Of_Contents"></a>Table Of Contents</h3>
 <ul>
 <li><a href="#Build_Lifecycle_Basics">Build Lifecycle Basics</a></li>
@@ -154,98 +153,90 @@
 <li><a href="#Packaging">Packaging</a></li>
 <li><a href="#Plugins">Plugins</a></li></ul></li>
 <li><a href="#Lifecycle_Reference">Lifecycle Reference</a></li>
-<li><a href="#Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></li></ul></div>
-<div class="section">
+<li><a href="#Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></li></ul></section><section>
 <h3><a name="Build_Lifecycle_Basics">Build Lifecycle Basics</a></h3>
 <p>Maven is based around the central concept of a build lifecycle. What this means is that the process for building and distributing a particular artifact (project) is clearly defined.</p>
 <p>For the person building a project, this means that it is only necessary to learn a small set of commands to build any Maven project, and the <a href="./introduction-to-the-pom.html">POM</a> will ensure they get the results they desired.</p>
-<p>There are three built-in build lifecycles: default, clean and site. The <tt>default</tt> lifecycle handles your project deployment, the <tt>clean</tt> lifecycle handles project cleaning, while the <tt>site</tt> lifecycle handles the creation of your project's site documentation.</p>
-<div class="section">
+<p>There are three built-in build lifecycles: default, clean and site. The <code>default</code> lifecycle handles your project deployment, the <code>clean</code> lifecycle handles project cleaning, while the <code>site</code> lifecycle handles the creation of your project's site documentation.</p><section>
 <h4><a name="A_Build_Lifecycle_is_Made_Up_of_Phases">A Build Lifecycle is Made Up of Phases</a></h4>
 <p>Each of these build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.</p>
 <p>For example, the default lifecycle comprises of the following phases (for a complete list of the lifecycle phases, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>):</p>
 <ul>
-<li><tt>validate</tt> - validate the project is correct and all necessary information is available</li>
-<li><tt>compile</tt> - compile the source code of the project</li>
-<li><tt>test</tt> - test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed</li>
-<li><tt>package</tt> - take the compiled code and package it in its distributable format, such as a JAR.</li>
-<li><tt>verify</tt> - run any checks on results of integration tests to ensure quality criteria are met</li>
-<li><tt>install</tt> - install the package into the local repository, for use as a dependency in other projects locally</li>
-<li><tt>deploy</tt> - done in the build environment, copies the final package to the remote repository for sharing with other developers and projects.</li></ul>
-<p>These lifecycle phases (plus the other lifecycle phases not shown here) are executed sequentially to complete the <tt>default</tt> lifecycle. Given the lifecycle phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the integration tests, install the verified package to the local repository, then deploy the installed package to a remote repository.</p>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
-<div class="section">
+<li><code>validate</code> - validate the project is correct and all necessary information is available</li>
+<li><code>compile</code> - compile the source code of the project</li>
+<li><code>test</code> - test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed</li>
+<li><code>package</code> - take the compiled code and package it in its distributable format, such as a JAR.</li>
+<li><code>verify</code> - run any checks on results of integration tests to ensure quality criteria are met</li>
+<li><code>install</code> - install the package into the local repository, for use as a dependency in other projects locally</li>
+<li><code>deploy</code> - done in the build environment, copies the final package to the remote repository for sharing with other developers and projects.</li></ul>
+<p>These lifecycle phases (plus the other lifecycle phases not shown here) are executed sequentially to complete the <code>default</code> lifecycle. Given the lifecycle phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the integration tests, install the verified package to the local repository, then deploy the installed package to a remote repository.</p>
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section><section>
 <h4><a name="Usual_Command_Line_Calls">Usual Command Line Calls</a></h4>
 <p>In a development environment, use the following call to build and install artifacts into the local repository.</p>
 <div>
 <pre>mvn install</pre></div>
-<p>This command executes each default life cycle phase in order (<tt>validate</tt>, <tt>compile</tt>, <tt>package</tt>, etc.), before executing <tt>install</tt>. You only need to call the last build phase to be executed, in this case, <tt>install</tt>:</p>
+<p>This command executes each default life cycle phase in order (<code>validate</code>, <code>compile</code>, <code>package</code>, etc.), before executing <code>install</code>. You only need to call the last build phase to be executed, in this case, <code>install</code>:</p>
 <p>In a build environment, use the following call to cleanly build and deploy artifacts into the shared repository.</p>
 <div>
 <pre>mvn clean deploy</pre></div>
-<p>The same command can be used in a multi-module scenario (i.e. a project with one or more subprojects). Maven traverses into every subproject and executes <tt>clean</tt>, then executes <tt>deploy</tt> (including all of the prior build phase steps).</p>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
-<div class="section">
+<p>The same command can be used in a multi-module scenario (i.e. a project with one or more subprojects). Maven traverses into every subproject and executes <code>clean</code>, then executes <code>deploy</code> (including all of the prior build phase steps).</p>
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section><section>
 <h4><a name="A_Build_Phase_is_Made_Up_of_Plugin_Goals">A Build Phase is Made Up of Plugin Goals</a></h4>
 <p>However, even though a build phase is responsible for a specific step in the build lifecycle, the manner in which it carries out those responsibilities may vary. And this is done by declaring the plugin goals bound to those build phases.</p>
-<p>A plugin goal represents a specific task (finer than a build phase) which contributes to the building and managing of a project. It may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation. The order of execution depends on the order in which the goal(s) and the build phase(s) are invoked. For example, consider the command below. The <tt>clean</tt> and <tt>package</tt> arguments are build phases, while the <tt>dependency:copy-dependencies</tt> is a goal (of a plugin).</p>
+<p>A plugin goal represents a specific task (finer than a build phase) which contributes to the building and managing of a project. It may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation. The order of execution depends on the order in which the goal(s) and the build phase(s) are invoked. For example, consider the command below. The <code>clean</code> and <code>package</code> arguments are build phases, while the <code>dependency:copy-dependencies</code> is a goal (of a plugin).</p>
 <div>
 <pre>mvn clean dependency:copy-dependencies package</pre></div>
-<p>If this were to be executed, the <tt>clean</tt> phase will be executed first (meaning it will run all preceding phases of the clean lifecycle, plus the <tt>clean</tt> phase itself), and then the <tt>dependency:copy-dependencies</tt> goal, before finally executing the <tt>package</tt> phase (and all its preceding build phases of the default lifecycle).</p>
+<p>If this were to be executed, the <code>clean</code> phase will be executed first (meaning it will run all preceding phases of the clean lifecycle, plus the <code>clean</code> phase itself), and then the <code>dependency:copy-dependencies</code> goal, before finally executing the <code>package</code> phase (and all its preceding build phases of the default lifecycle).</p>
 <p>Moreover, if a goal is bound to one or more build phases, that goal will be called in all those phases.</p>
 <p>Furthermore, a build phase can also have zero or more goals bound to it. If a build phase has no goals bound to it, that build phase will not execute. But if it has one or more goals bound to it, it will execute all those goals</p>
 <p>(<i>Note: In Maven 2.0.5 and above, multiple goals bound to a phase are executed in the same order as they are declared in the POM, however multiple instances of the same plugin are not supported. Multiple instances of the same plugin are grouped to execute together and ordered in Maven 2.0.11 and above</i>).</p>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
-<div class="section">
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section><section>
 <h4><a name="Some_Phases_Are_Not_Usually_Called_From_the_Command_Line">Some Phases Are Not Usually Called From the Command Line</a></h4>
-<p>The phases named with hyphenated-words (<tt>pre-*</tt>, <tt>post-*</tt>, or <tt>process-*</tt>) are not usually directly called from the command line. These phases sequence the build, producing intermediate results that are not useful outside the build. In the case of invoking <tt>integration-test</tt>, the environment may be left in a hanging state.</p>
-<p>Code coverage tools such as Jacoco and execution container plugins such as Tomcat, Cargo, and Docker bind goals to the <tt>pre-integration-test</tt> phase to prepare the integration test container environment. These plugins also bind goals to the <tt>post-integration-test</tt> phase to collect coverage statistics or decommission the integration test container.</p>
-<p>Failsafe and code coverage plugins bind goals to <tt>integration-test</tt> and <tt>verify</tt> phases. The net result is test and coverage reports are available after the <tt>verify</tt> phase. If <tt>integration-test</tt> were to be called from the command line, no reports are generated. Worse is that the integration test container environment is left in a hanging state; the Tomcat webserver or Docker instance is left running, and Maven may not even terminate by itself.</p>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div></div>
-<div class="section">
+<p>The phases named with hyphenated-words (<code>pre-*</code>, <code>post-*</code>, or <code>process-*</code>) are not usually directly called from the command line. These phases sequence the build, producing intermediate results that are not useful outside the build. In the case of invoking <code>integration-test</code>, the environment may be left in a hanging state.</p>
+<p>Code coverage tools such as Jacoco and execution container plugins such as Tomcat, Cargo, and Docker bind goals to the <code>pre-integration-test</code> phase to prepare the integration test container environment. These plugins also bind goals to the <code>post-integration-test</code> phase to collect coverage statistics or decommission the integration test container.</p>
+<p>Failsafe and code coverage plugins bind goals to <code>integration-test</code> and <code>verify</code> phases. The net result is test and coverage reports are available after the <code>verify</code> phase. If <code>integration-test</code> were to be called from the command line, no reports are generated. Worse is that the integration test container environment is left in a hanging state; the Tomcat webserver or Docker instance is left running, and Maven may not even terminate by itself.</p>
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section></section><section>
 <h3><a name="Setting_Up_Your_Project_to_Use_the_Build_Lifecycle">Setting Up Your Project to Use the Build Lifecycle</a></h3>
-<p>The build lifecycle is simple enough to use, but when you are constructing a Maven build for a project, how do you go about assigning tasks to each of those build phases?</p>
-<div class="section">
+<p>The build lifecycle is simple enough to use, but when you are constructing a Maven build for a project, how do you go about assigning tasks to each of those build phases?</p><section>
 <h4><a name="Packaging">Packaging</a></h4>
-<p>The first, and most common way, is to set the packaging for your project via the equally named POM element <tt>&lt;packaging&gt;</tt>. Some of the valid packaging values are <tt>jar</tt>, <tt>war</tt>, <tt>ear</tt> and <tt>pom</tt>. If no packaging value has been specified, it will default to <tt>jar</tt>.</p>
-<p>Each packaging contains a list of goals to bind to a particular phase. For example, the <tt>jar</tt> packaging will bind the following goals to build phases of the default lifecycle.</p>
+<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 border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>process-resources</tt></td>
-<td align="left"><tt>resources:resources</tt></td></tr>
+<td align="left"><code>process-resources</code></td>
+<td align="left"><code>resources:resources</code></td></tr>
 <tr class="a">
-<td align="left"><tt>compile</tt></td>
-<td align="left"><tt>compiler:compile</tt></td></tr>
+<td align="left"><code>compile</code></td>
+<td align="left"><code>compiler:compile</code></td></tr>
 <tr class="b">
-<td align="left"><tt>process-test-resources</tt></td>
-<td align="left"><tt>resources:testResources</tt></td></tr>
+<td align="left"><code>process-test-resources</code></td>
+<td align="left"><code>resources:testResources</code></td></tr>
 <tr class="a">
-<td align="left"><tt>test-compile</tt></td>
-<td align="left"><tt>compiler:testCompile</tt></td></tr>
+<td align="left"><code>test-compile</code></td>
+<td align="left"><code>compiler:testCompile</code></td></tr>
 <tr class="b">
-<td align="left"><tt>test</tt></td>
-<td align="left"><tt>surefire:test</tt></td></tr>
+<td align="left"><code>test</code></td>
+<td align="left"><code>surefire:test</code></td></tr>
 <tr class="a">
-<td align="left"><tt>package</tt></td>
-<td align="left"><tt>jar:jar</tt></td></tr>
+<td align="left"><code>package</code></td>
+<td align="left"><code>jar:jar</code></td></tr>
 <tr class="b">
-<td align="left"><tt>install</tt></td>
-<td align="left"><tt>install:install</tt></td></tr>
+<td align="left"><code>install</code></td>
+<td align="left"><code>install:install</code></td></tr>
 <tr class="a">
-<td align="left"><tt>deploy</tt></td>
-<td align="left"><tt>deploy:deploy</tt></td></tr></table>
-<p>This is an almost <a href="/ref/current/maven-core/default-bindings.html">standard set of bindings</a>; however, some packagings handle them differently. For example, a project that is purely metadata (packaging value is <tt>pom</tt>) only binds goals to the <tt>install</tt> and <tt>deploy</tt> phases (for a complete list of goal-to-build-phase bindings of some of the packaging types, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>).</p>
-<p>Note that for some packaging types to be available, you may also need to include a particular plugin in the <tt>&lt;build&gt;</tt> section of your POM and specify <tt>&lt;extensions&gt;true&lt;/extensions&gt;</tt> for that plugin. One example of a plugin that requires this is the Plexus plugin, which provides a <tt>plexus-application</tt> and <tt>plexus-service</tt> packaging.</p>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
-<div class="section">
+<td align="left"><code>deploy</code></td>
+<td align="left"><code>deploy:deploy</code></td></tr></table>
+<p>This is an almost <a href="/ref/current/maven-core/default-bindings.html">standard set of bindings</a>; however, some packagings handle them differently. For example, a project that is purely metadata (packaging value is <code>pom</code>) only binds goals to the <code>install</code> and <code>deploy</code> phases (for a complete list of goal-to-build-phase bindings of some of the packaging types, refer to the <a href="#Lifecycle_Reference">Lifecycle Reference</a>).</p>
+<p>Note that for some packaging types to be available, you may also need to include a particular plugin in the <code>&lt;build&gt;</code> section of your POM and specify <code>&lt;extensions&gt;true&lt;/extensions&gt;</code> for that plugin. One example of a plugin that requires this is the Plexus plugin, which provides a <code>plexus-application</code> and <code>plexus-service</code> packaging.</p>
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section><section>
 <h4><a name="Plugins">Plugins</a></h4>
-<p>The second way to add goals to phases is to configure plugins in your project. Plugins are artifacts that provide goals to Maven. Furthermore, a plugin may have one or more goals wherein each goal represents a capability of that plugin. For example, the Compiler plugin has two goals: <tt>compile</tt> and <tt>testCompile</tt>. The former compiles the source code of your main code, while the latter compiles the source code of your test code.</p>
+<p>The second way to add goals to phases is to configure plugins in your project. Plugins are artifacts that provide goals to Maven. Furthermore, a plugin may have one or more goals wherein each goal represents a capability of that plugin. For example, the Compiler plugin has two goals: <code>compile</code> and <code>testCompile</code>. The former compiles the source code of your main code, while the latter compiles the source code of your test code.</p>
 <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 <tt>&lt;executions&gt;</tt> element to gain more control over the order of particular goals.</p>
-<p>For example, the Modello plugin binds by default its goal <tt>modello:java</tt> to the <tt>generate-sources</tt> phase (Note: The <tt>modello:java</tt> 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 <tt>&lt;plugins&gt;</tt> section of <tt>&lt;build&gt;</tt>:</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>
 <pre>...
  &lt;plugin&gt;
@@ -267,9 +258,9 @@
    &lt;/executions&gt;
  &lt;/plugin&gt;
 ...</pre></div>
-<p>You might be wondering why that <tt>&lt;executions&gt;</tt> 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>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 <tt>modello:java</tt>, it only makes sense in the <tt>generate-sources</tt> 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 <tt>display:time</tt> that echos the current time to the commandline, and you want it to run in the <tt>process-test-resources</tt> phase to indicate when the tests were started. This would be configured like so:</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>
 <pre>...
  &lt;plugin&gt;
@@ -286,23 +277,22 @@
    &lt;/executions&gt;
  &lt;/plugin&gt;
 ...</pre></div>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div></div>
-<div class="section">
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section></section><section>
 <h3><a name="Lifecycle_Reference">Lifecycle Reference</a></h3>
-<p>The following lists all build phases of the <tt>default</tt>, <tt>clean</tt> and <tt>site</tt> lifecycles, which are executed in the order given up to the point of the one specified.</p>
+<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>
 <p><b>Clean Lifecycle</b></p>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">Description</th></tr>
 <tr class="b">
-<td align="left"><tt>pre-clean</tt></td>
+<td align="left"><code>pre-clean</code></td>
 <td align="left">execute processes needed prior to the actual project cleaning</td></tr>
 <tr class="a">
-<td align="left"><tt>clean</tt></td>
+<td align="left"><code>clean</code></td>
 <td align="left">remove all files generated by the previous build</td></tr>
 <tr class="b">
-<td align="left"><tt>post-clean</tt></td>
+<td align="left"><code>post-clean</code></td>
 <td align="left">execute processes needed to finalize the project cleaning</td></tr></table>
 <p><b>Default Lifecycle</b></p>
 <table border="1" class="table table-striped">
@@ -310,73 +300,73 @@
 <th align="left">Phase</th>
 <th align="left">Description</th></tr>
 <tr class="b">
-<td align="left"><tt>validate</tt></td>
+<td align="left"><code>validate</code></td>
 <td align="left">validate the project is correct and all necessary information is available.</td></tr>
 <tr class="a">
-<td align="left"><tt>initialize</tt></td>
+<td align="left"><code>initialize</code></td>
 <td align="left">initialize build state, e.g. set properties or create directories.</td></tr>
 <tr class="b">
-<td align="left"><tt>generate-sources</tt></td>
+<td align="left"><code>generate-sources</code></td>
 <td align="left">generate any source code for inclusion in compilation.</td></tr>
 <tr class="a">
-<td align="left"><tt>process-sources</tt></td>
+<td align="left"><code>process-sources</code></td>
 <td align="left">process the source code, for example to filter any values.</td></tr>
 <tr class="b">
-<td align="left"><tt>generate-resources</tt></td>
+<td align="left"><code>generate-resources</code></td>
 <td align="left">generate resources for inclusion in the package.</td></tr>
 <tr class="a">
-<td align="left"><tt>process-resources</tt></td>
+<td align="left"><code>process-resources</code></td>
 <td align="left">copy and process the resources into the destination directory, ready for packaging.</td></tr>
 <tr class="b">
-<td align="left"><tt>compile</tt></td>
+<td align="left"><code>compile</code></td>
 <td align="left">compile the source code of the project.</td></tr>
 <tr class="a">
-<td align="left"><tt>process-classes</tt></td>
+<td align="left"><code>process-classes</code></td>
 <td align="left">post-process the generated files from compilation, for example to do bytecode enhancement on Java classes.</td></tr>
 <tr class="b">
-<td align="left"><tt>generate-test-sources</tt></td>
+<td align="left"><code>generate-test-sources</code></td>
 <td align="left">generate any test source code for inclusion in compilation.</td></tr>
 <tr class="a">
-<td align="left"><tt>process-test-sources</tt></td>
+<td align="left"><code>process-test-sources</code></td>
 <td align="left">process the test source code, for example to filter any values.</td></tr>
 <tr class="b">
-<td align="left"><tt>generate-test-resources</tt></td>
+<td align="left"><code>generate-test-resources</code></td>
 <td align="left">create resources for testing.</td></tr>
 <tr class="a">
-<td align="left"><tt>process-test-resources</tt></td>
+<td align="left"><code>process-test-resources</code></td>
 <td align="left">copy and process the resources into the test destination directory.</td></tr>
 <tr class="b">
-<td align="left"><tt>test-compile</tt></td>
+<td align="left"><code>test-compile</code></td>
 <td align="left">compile the test source code into the test destination directory</td></tr>
 <tr class="a">
-<td align="left"><tt>process-test-classes</tt></td>
+<td align="left"><code>process-test-classes</code></td>
 <td align="left">post-process the generated files from test compilation, for example to do bytecode enhancement on Java classes. For Maven 2.0.5 and above.</td></tr>
 <tr class="b">
-<td align="left"><tt>test</tt></td>
+<td align="left"><code>test</code></td>
 <td align="left">run tests using a suitable unit testing framework. These tests should not require the code be packaged or deployed.</td></tr>
 <tr class="a">
-<td align="left"><tt>prepare-package</tt></td>
+<td align="left"><code>prepare-package</code></td>
 <td align="left">perform any operations necessary to prepare a package before the actual packaging. This often results in an unpacked, processed version of the package. (Maven 2.1 and above)</td></tr>
 <tr class="b">
-<td align="left"><tt>package</tt></td>
+<td align="left"><code>package</code></td>
 <td align="left">take the compiled code and package it in its distributable format, such as a JAR.</td></tr>
 <tr class="a">
-<td align="left"><tt>pre-integration-test</tt></td>
+<td align="left"><code>pre-integration-test</code></td>
 <td align="left">perform actions required before integration tests are executed. This may involve things such as setting up the required environment.</td></tr>
 <tr class="b">
-<td align="left"><tt>integration-test</tt></td>
+<td align="left"><code>integration-test</code></td>
 <td align="left">process and deploy the package if necessary into an environment where integration tests can be run.</td></tr>
 <tr class="a">
-<td align="left"><tt>post-integration-test</tt></td>
+<td align="left"><code>post-integration-test</code></td>
 <td align="left">perform actions required after integration tests have been executed. This may including cleaning up the environment.</td></tr>
 <tr class="b">
-<td align="left"><tt>verify</tt></td>
+<td align="left"><code>verify</code></td>
 <td align="left">run any checks to verify the package is valid and meets quality criteria.</td></tr>
 <tr class="a">
-<td align="left"><tt>install</tt></td>
+<td align="left"><code>install</code></td>
 <td align="left">install the package into the local repository, for use as a dependency in other projects locally.</td></tr>
 <tr class="b">
-<td align="left"><tt>deploy</tt></td>
+<td align="left"><code>deploy</code></td>
 <td 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>
 <p><b>Site Lifecycle</b></p>
 <table border="1" class="table table-striped">
@@ -384,147 +374,139 @@
 <th align="left">Phase</th>
 <th align="left">Description</th></tr>
 <tr class="b">
-<td align="left"><tt>pre-site</tt></td>
+<td align="left"><code>pre-site</code></td>
 <td align="left">execute processes needed prior to the actual project site generation</td></tr>
 <tr class="a">
-<td align="left"><tt>site</tt></td>
+<td align="left"><code>site</code></td>
 <td align="left">generate the project's site documentation</td></tr>
 <tr class="b">
-<td align="left"><tt>post-site</tt></td>
+<td align="left"><code>post-site</code></td>
 <td align="left">execute processes needed to finalize the site generation, and to prepare for site deployment</td></tr>
 <tr class="a">
-<td align="left"><tt>site-deploy</tt></td>
+<td align="left"><code>site-deploy</code></td>
 <td align="left">deploy the generated site documentation to the specified web server</td></tr></table>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div>
-<div class="section">
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section><section>
 <h3><a name="Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></h3>
-<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>
-<div class="section">
+<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>
 <h4><a name="Clean_Lifecycle_Bindings"></a>Clean Lifecycle Bindings</h4>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>clean</tt></td>
-<td align="left"><tt>clean:clean</tt></td></tr></table></div>
-<div class="section">
-<h4><a name="Default_Lifecycle_Bindings_-_Packaging_ejb_.2F_ejb3_.2F_jar_.2F_par_.2F_rar_.2F_war"></a>Default Lifecycle Bindings - Packaging <tt>ejb</tt> / <tt>ejb3</tt> / <tt>jar</tt> / <tt>par</tt> / <tt>rar</tt> / <tt>war</tt></h4>
+<td align="left"><code>clean</code></td>
+<td align="left"><code>clean:clean</code></td></tr></table></section><section>
+<h4><a name="Default_Lifecycle_Bindings_-_Packaging_ejb_.2F_ejb3_.2F_jar_.2F_par_.2F_rar_.2F_war"></a>Default Lifecycle Bindings - Packaging <code>ejb</code> / <code>ejb3</code> / <code>jar</code> / <code>par</code> / <code>rar</code> / <code>war</code></h4>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>process-resources</tt></td>
-<td align="left"><tt>resources:resources</tt></td></tr>
+<td align="left"><code>process-resources</code></td>
+<td align="left"><code>resources:resources</code></td></tr>
 <tr class="a">
-<td align="left"><tt>compile</tt></td>
-<td align="left"><tt>compiler:compile</tt></td></tr>
+<td align="left"><code>compile</code></td>
+<td align="left"><code>compiler:compile</code></td></tr>
 <tr class="b">
-<td align="left"><tt>process-test-resources</tt></td>
-<td align="left"><tt>resources:testResources</tt></td></tr>
+<td align="left"><code>process-test-resources</code></td>
+<td align="left"><code>resources:testResources</code></td></tr>
 <tr class="a">
-<td align="left"><tt>test-compile</tt></td>
-<td align="left"><tt>compiler:testCompile</tt></td></tr>
+<td align="left"><code>test-compile</code></td>
+<td align="left"><code>compiler:testCompile</code></td></tr>
 <tr class="b">
-<td align="left"><tt>test</tt></td>
-<td align="left"><tt>surefire:test</tt></td></tr>
+<td align="left"><code>test</code></td>
+<td align="left"><code>surefire:test</code></td></tr>
 <tr class="a">
-<td align="left"><tt>package</tt></td>
-<td align="left"><tt>ejb:ejb</tt> <i>or</i> <tt>ejb3:ejb3</tt> <i>or</i> <tt>jar:jar</tt> <i>or</i> <tt>par:par</tt> <i>or</i> <tt>rar:rar</tt> <i>or</i> <tt>war:war</tt></td></tr>
+<td align="left"><code>package</code></td>
+<td align="left"><code>ejb:ejb</code> <i>or</i> <code>ejb3:ejb3</code> <i>or</i> <code>jar:jar</code> <i>or</i> <code>par:par</code> <i>or</i> <code>rar:rar</code> <i>or</i> <code>war:war</code></td></tr>
 <tr class="b">
-<td align="left"><tt>install</tt></td>
-<td align="left"><tt>install:install</tt></td></tr>
+<td align="left"><code>install</code></td>
+<td align="left"><code>install:install</code></td></tr>
 <tr class="a">
-<td align="left"><tt>deploy</tt></td>
-<td align="left"><tt>deploy:deploy</tt></td></tr></table></div>
-<div class="section">
-<h4><a name="Default_Lifecycle_Bindings_-_Packaging_ear"></a>Default Lifecycle Bindings - Packaging <tt>ear</tt></h4>
+<td align="left"><code>deploy</code></td>
+<td align="left"><code>deploy:deploy</code></td></tr></table></section><section>
+<h4><a name="Default_Lifecycle_Bindings_-_Packaging_ear"></a>Default Lifecycle Bindings - Packaging <code>ear</code></h4>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>generate-resources</tt></td>
-<td align="left"><tt>ear:generate-application-xml</tt></td></tr>
+<td align="left"><code>generate-resources</code></td>
+<td align="left"><code>ear:generate-application-xml</code></td></tr>
 <tr class="a">
-<td align="left"><tt>process-resources</tt></td>
-<td align="left"><tt>resources:resources</tt></td></tr>
+<td align="left"><code>process-resources</code></td>
+<td align="left"><code>resources:resources</code></td></tr>
 <tr class="b">
-<td align="left"><tt>package</tt></td>
-<td align="left"><tt>ear:ear</tt></td></tr>
+<td align="left"><code>package</code></td>
+<td align="left"><code>ear:ear</code></td></tr>
 <tr class="a">
-<td align="left"><tt>install</tt></td>
-<td align="left"><tt>install:install</tt></td></tr>
-<tr class="b">
-<td align="left"><tt>deploy</tt></td>
-<td align="left"><tt>deploy:deploy</tt></td></tr></table></div>
-<div class="section">
-<h4><a name="Default_Lifecycle_Bindings_-_Packaging_maven-plugin"></a>Default Lifecycle Bindings - Packaging <tt>maven-plugin</tt></h4>
+<td align="left"><code>install</code></td>
+<td align="left"><code>install:install</code></td></tr>
+<tr class="b">
+<td align="left"><code>deploy</code></td>
+<td align="left"><code>deploy:deploy</code></td></tr></table></section><section>
+<h4><a name="Default_Lifecycle_Bindings_-_Packaging_maven-plugin"></a>Default Lifecycle Bindings - Packaging <code>maven-plugin</code></h4>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>generate-resources</tt></td>
-<td align="left"><tt>plugin:descriptor</tt></td></tr>
+<td align="left"><code>generate-resources</code></td>
+<td align="left"><code>plugin:descriptor</code></td></tr>
 <tr class="a">
-<td align="left"><tt>process-resources</tt></td>
-<td align="left"><tt>resources:resources</tt></td></tr>
+<td align="left"><code>process-resources</code></td>
+<td align="left"><code>resources:resources</code></td></tr>
 <tr class="b">
-<td align="left"><tt>compile</tt></td>
-<td align="left"><tt>compiler:compile</tt></td></tr>
+<td align="left"><code>compile</code></td>
+<td align="left"><code>compiler:compile</code></td></tr>
 <tr class="a">
-<td align="left"><tt>process-test-resources</tt></td>
-<td align="left"><tt>resources:testResources</tt></td></tr>
+<td align="left"><code>process-test-resources</code></td>
+<td align="left"><code>resources:testResources</code></td></tr>
 <tr class="b">
-<td align="left"><tt>test-compile</tt></td>
-<td align="left"><tt>compiler:testCompile</tt></td></tr>
+<td align="left"><code>test-compile</code></td>
+<td align="left"><code>compiler:testCompile</code></td></tr>
 <tr class="a">
-<td align="left"><tt>test</tt></td>
-<td align="left"><tt>surefire:test</tt></td></tr>
+<td align="left"><code>test</code></td>
+<td align="left"><code>surefire:test</code></td></tr>
 <tr class="b">
-<td align="left"><tt>package</tt></td>
-<td align="left"><tt>jar:jar</tt> <i>and</i> <tt>plugin:addPluginArtifactMetadata</tt></td></tr>
+<td align="left"><code>package</code></td>
+<td align="left"><code>jar:jar</code> <i>and</i> <code>plugin:addPluginArtifactMetadata</code></td></tr>
 <tr class="a">
-<td align="left"><tt>install</tt></td>
-<td align="left"><tt>install:install</tt></td></tr>
+<td align="left"><code>install</code></td>
+<td align="left"><code>install:install</code></td></tr>
 <tr class="b">
-<td align="left"><tt>deploy</tt></td>
-<td align="left"><tt>deploy:deploy</tt></td></tr></table></div>
-<div class="section">
-<h4><a name="Default_Lifecycle_Bindings_-_Packaging_pom"></a>Default Lifecycle Bindings - Packaging <tt>pom</tt></h4>
+<td align="left"><code>deploy</code></td>
+<td align="left"><code>deploy:deploy</code></td></tr></table></section><section>
+<h4><a name="Default_Lifecycle_Bindings_-_Packaging_pom"></a>Default Lifecycle Bindings - Packaging <code>pom</code></h4>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>package</tt></td>
+<td align="left"><code>package</code></td>
 <td align="left"></td></tr>
 <tr class="a">
-<td align="left"><tt>install</tt></td>
-<td align="left"><tt>install:install</tt></td></tr>
+<td align="left"><code>install</code></td>
+<td align="left"><code>install:install</code></td></tr>
 <tr class="b">
-<td align="left"><tt>deploy</tt></td>
-<td align="left"><tt>deploy:deploy</tt></td></tr></table></div>
-<div class="section">
+<td align="left"><code>deploy</code></td>
+<td align="left"><code>deploy:deploy</code></td></tr></table></section><section>
 <h4><a name="Site_Lifecycle_Bindings"></a>Site Lifecycle Bindings</h4>
 <table border="1" class="table table-striped">
 <tr class="a">
 <th align="left">Phase</th>
 <th align="left">plugin:goal</th></tr>
 <tr class="b">
-<td align="left"><tt>site</tt></td>
-<td align="left"><tt>site:site</tt></td></tr>
+<td align="left"><code>site</code></td>
+<td align="left"><code>site:site</code></td></tr>
 <tr class="a">
-<td align="left"><tt>site-deploy</tt></td>
-<td align="left"><tt>site:deploy</tt></td></tr></table></div>
-<div class="section">
+<td align="left"><code>site-deploy</code></td>
+<td align="left"><code>site:deploy</code></td></tr></table></section><section>
 <h4><a name="References"></a>References</h4>
-<p>The full Maven lifecycle is defined by the <tt>components.xml</tt> file in the <tt>maven-core</tt> module, with <a href="/ref/current/maven-core/lifecycles.html">associated documentation</a> for reference.</p>
-<p>Default lifecycle bindings are defined in a separate <tt><a class="externalLink" href="https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml">default-bindings.xml</a></tt> descriptor.</p>
+<p>The full Maven lifecycle is defined by the <code>components.xml</code> file in the <code>maven-core</code> module, with <a href="/ref/current/maven-core/lifecycles.html">associated documentation</a> for reference.</p>
+<p>Default lifecycle bindings are defined in a separate <code><a class="externalLink" href="https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml">default-bindings.xml</a></code> descriptor.</p>
 <p>See <a href="/ref/current/maven-core/lifecycles.html">Lifecycles Reference</a> and <a href="/ref/current/maven-core/default-bindings.html">Plugin Bindings for default Lifecycle Reference</a> for latest documentation taken directly from source code.</p>
-<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></div></div></div>
+<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section></section></section>
         </div>
       </div>
     </div>

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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/introduction/introduction-to-the-pom.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/introduction/introduction-to-the-pom.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -145,7 +145,7 @@ Brett Porter" />
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Introduction_to_the_POM"></a>Introduction to the POM</h2>
 <ul>
 <li><a href="./introduction-to-the-pom.html#What_is_a_POM">What is a POM</a>?</li>
@@ -164,13 +164,11 @@ Brett Porter" />
 <li><a href="./introduction-to-the-pom.html#Example_5">Example 5</a></li></ul></li>
 <li><a href="./introduction-to-the-pom.html#Project_Interpolation">Project Interpolation and Variables</a>
 <ul>
-<li><a href="./introduction-to-the-pom.html#Available_Variables">Available Variables</a></li></ul></li></ul>
-<div class="section">
+<li><a href="./introduction-to-the-pom.html#Available_Variables">Available Variables</a></li></ul></li></ul><section>
 <h3><a name="What_is_a_POM.3F"></a><a name="What_is_a_POM">What is a POM</a>?</h3>
-<p>A Project Object Model or POM is the fundamental unit of work in Maven. It is an XML file that contains information about the project and configuration details used by Maven to build the project. It contains default values for most projects. Examples for this is the build directory, which is <tt>target</tt>; the source directory, which is <tt>src/main/java</tt>; the test source directory, which is <tt>src/test/java</tt>; and so on. When executing a task or goal, Maven looks for the POM in the current directory. It reads the POM, gets the needed configuration information, then executes the goal.</p>
+<p>A Project Object Model or POM is the fundamental unit of work in Maven. It is an XML file that contains information about the project and configuration details used by Maven to build the project. It contains default values for most projects. Examples for this is the build directory, which is <code>target</code>; the source directory, which is <code>src/main/java</code>; the test source directory, which is <code>src/test/java</code>; and so on. When executing a task or goal, Maven looks for the POM in the current directory. It reads the POM, gets the needed configuration information, then executes the goal.</p>
 <p>Some of the configuration that can be specified in the POM are the project dependencies, the plugins or goals that can be executed, the build profiles, and so on. Other information such as the project version, description, developers, mailing lists and such can also be specified.</p>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section><section>
 <h3><a name="Super_POM">Super POM</a></h3>
 <p>The Super POM is Maven's default POM. All POMs extend the Super POM unless explicitly set, meaning the configuration specified in the Super POM is inherited by the POMs you created for your projects. The snippet below is the Super POM for Maven 3.5.4.</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
@@ -301,8 +299,7 @@ Brett Porter" />
 
 &lt;/project&gt;
 </pre></div>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section><section>
 <h3><a name="Minimal_POM">Minimal POM</a></h3>
 <p>The minimum requirement for a POM are the following:</p>
 <ul>
@@ -320,9 +317,8 @@ Brett Porter" />
 &lt;/project&gt;</pre></div>
 <p>A POM requires that its groupId, artifactId, and version be configured. These three values form the project's fully qualified artifact name. This is in the form of &lt;groupId&gt;:&lt;artifactId&gt;:&lt;version&gt;. As for the example above, its fully qualified artifact name is &quot;com.mycompany.app:my-app:1&quot;.</p>
 <p>Also, as mentioned in the <a href="#What_is_a_POM">first section</a>, if the configuration details are not specified, Maven will use their defaults. One of these default values is the packaging type. Every Maven project has a packaging type. If it is not specified in the POM, then the default value &quot;jar&quot; would be used.</p>
-<p>Furthermore, you can see that in the minimal POM the <i>repositories</i> were not specified. If you build your project using the minimal POM, it would inherit the <i>repositories</i> configuration in the Super POM. Therefore when Maven sees the dependencies in the minimal POM, it would know that these dependencies will be downloaded from <tt>http://repo.maven.apache.org/maven2</tt> which was specified in the Super POM.</p>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div>
-<div class="section">
+<p>Furthermore, you can see that in the minimal POM the <i>repositories</i> were not specified. If you build your project using the minimal POM, it would inherit the <i>repositories</i> configuration in the Super POM. Therefore when Maven sees the dependencies in the minimal POM, it would know that these dependencies will be downloaded from <code>http://repo.maven.apache.org/maven2</code> which was specified in the Super POM.</p>
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section><section>
 <h3><a name="Project_Inheritance">Project Inheritance</a></h3>
 <p>Elements in the POM that are merged are the following:</p>
 <ul>
@@ -332,10 +328,8 @@ Brett Porter" />
 <li>plugin executions with matching ids</li>
 <li>plugin configuration</li>
 <li>resources</li></ul>
-<p>The Super POM is one example of project inheritance, however you can also introduce your own parent POMs by specifying the parent element in the POM, as demonstrated in the following examples.</p>
-<div class="section">
-<h4><a name="Example_1">Example 1</a></h4>
-<div class="section">
+<p>The Super POM is one example of project inheritance, however you can also introduce your own parent POMs by specifying the parent element in the POM, as demonstrated in the following examples.</p><section>
+<h4><a name="Example_1">Example 1</a></h4><section>
 <h5><a name="The_Scenario"></a>The Scenario</h5>
 <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="source"><pre class="prettyprint linenums">&lt;project&gt;
@@ -349,8 +343,7 @@ Brett Porter" />
  |-- my-module
  |   `-- pom.xml
  `-- pom.xml</pre></div>
-<p><b>Note:</b> <tt>my-module/pom.xml</tt> is the POM of com.mycompany.app:my-module:1 while <tt>pom.xml</tt> is the POM of com.mycompany.app:my-app:1</p></div>
-<div class="section">
+<p><b>Note:</b> <code>my-module/pom.xml</code> is the POM of com.mycompany.app:my-module:1 while <code>pom.xml</code> is the POM of com.mycompany.app:my-app:1</p></section><section>
 <h5><a name="The_Solution"></a>The Solution</h5>
 <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>
@@ -377,21 +370,18 @@ Brett Porter" />
   &lt;artifactId&gt;my-module&lt;/artifactId&gt;
 &lt;/project&gt;</pre></div>
 <p>This allows the module to inherit the groupId and / or the version of its parent POM.</p>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div></div>
-<div class="section">
-<h4><a name="Example_2">Example 2</a></h4>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section></section><section>
+<h4><a name="Example_2">Example 2</a></h4><section>
 <h5><a name="The_Scenario"></a>The Scenario</h5>
-<p>However, that would work if the parent project was already installed in our local repository or was in that specific directory structure (parent <tt>pom.xml</tt> is one directory higher than that of the module's <tt>pom.xml</tt>).</p>
+<p>However, that would work if the parent project was already installed in our local repository or was in that specific directory structure (parent <code>pom.xml</code> is one directory higher than that of the module's <code>pom.xml</code>).</p>
 <p>But what if the parent is not yet installed and if the directory structure is as in the following example?</p>
 <div class="source"><pre class="prettyprint linenums">.
  |-- my-module
  |   `-- pom.xml
  `-- parent
-     `-- pom.xml</pre></div></div>
-<div class="section">
+     `-- pom.xml</pre></div></section><section>
 <h5><a name="The_Solution"></a>The Solution</h5>
-<p>To address this directory structure (or any other directory structure), we would have to add the <tt>&lt;relativePath&gt;</tt> element to our parent section.</p>
+<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="source"><pre class="prettyprint linenums">&lt;project&gt;
   &lt;parent&gt;
     &lt;groupId&gt;com.mycompany.app&lt;/groupId&gt;
@@ -402,17 +392,14 @@ Brett Porter" />
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
   &lt;artifactId&gt;my-module&lt;/artifactId&gt;
 &lt;/project&gt;</pre></div>
-<p>As the name suggests, it's the relative path from the module's <tt>pom.xml</tt> to the parent's <tt>pom.xml</tt>.</p></div></div></div>
-<div class="section">
+<p>As the name suggests, it's the relative path from the module's <code>pom.xml</code> to the parent's <code>pom.xml</code>.</p></section></section></section><section>
 <h3><a name="Project_Aggregation">Project Aggregation</a></h3>
 <p>Project Aggregation is similar to <a href="#Project_Inheritance">Project Inheritance</a>. But instead of specifying the parent POM from the module, it specifies the modules from the parent POM. By doing so, the parent project now knows its modules, and if a Maven command is invoked against the parent project, that Maven command will then be executed to the parent's modules as well. To do Project Aggregation, you must do the following:</p>
 <ul>
 <li>Change the parent POMs packaging to the value &quot;pom&quot;.</li>
 <li>Specify in the parent POM the directories of its modules (children POMs).</li></ul>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p>
-<div class="section">
-<h4><a name="Example_3">Example 3</a></h4>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p><section>
+<h4><a name="Example_3">Example 3</a></h4><section>
 <h5><a name="The_Scenario"></a>The Scenario</h5>
 <p>Given the previous original artifact POMs and directory structure:</p>
 <p><b>com.mycompany.app:my-app:1's POM</b></p>
@@ -433,8 +420,7 @@ Brett Porter" />
 <div class="source"><pre class="prettyprint linenums">.
  |-- my-module
  |   `-- pom.xml
- `-- pom.xml</pre></div></div>
-<div class="section">
+ `-- pom.xml</pre></div></section><section>
 <h5><a name="The_Solution"></a>The Solution</h5>
 <p>If we are to aggregate my-module into my-app, we would only have to modify my-app.</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
@@ -448,12 +434,10 @@ Brett Porter" />
     &lt;module&gt;my-module&lt;/module&gt;
   &lt;/modules&gt;
 &lt;/project&gt;</pre></div>
-<p>In the revised com.mycompany.app:my-app:1, the packaging section and the modules sections were added. For the packaging, its value was set to &quot;pom&quot;, and for the modules section, we have the element <tt>&lt;module&gt;my-module&lt;/module&gt;</tt>. The value of <tt>&lt;module&gt;</tt> is the relative path from the com.mycompany.app:my-app:1 to com.mycompany.app:my-module:1's POM (<i>by practice, we use the module's artifactId as the module directory's name</i>).</p>
+<p>In the revised com.mycompany.app:my-app:1, the packaging section and the modules sections were added. For the packaging, its value was set to &quot;pom&quot;, and for the modules section, we have the element <code>&lt;module&gt;my-module&lt;/module&gt;</code>. The value of <code>&lt;module&gt;</code> is the relative path from the com.mycompany.app:my-app:1 to com.mycompany.app:my-module:1's POM (<i>by practice, we use the module's artifactId as the module directory's name</i>).</p>
 <p>Now, whenever a Maven command processes com.mycompany.app:my-app:1, that same Maven command would be ran against com.mycompany.app:my-module:1 as well. Furthermore, some commands (goals specifically) handle project aggregation differently.</p>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div></div>
-<div class="section">
-<h4><a name="Example_4">Example 4</a></h4>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section></section><section>
+<h4><a name="Example_4">Example 4</a></h4><section>
 <h5><a name="The_Scenario"></a>The Scenario</h5>
 <p>But what if we change the directory structure to the following:</p>
 <div class="source"><pre class="prettyprint linenums">.
@@ -461,8 +445,7 @@ Brett Porter" />
  |   `-- pom.xml
  `-- parent
      `-- pom.xml</pre></div>
-<p>How would the parent POM specify its modules?</p></div>
-<div class="section">
+<p>How would the parent POM specify its modules?</p></section><section>
 <h5><a name="The_Solution"></a>The Solution</h5>
 <p>The answer? - the same way as Example 3, by specifying the path to the module.</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
@@ -475,8 +458,7 @@ Brett Porter" />
   &lt;modules&gt;
     &lt;module&gt;../my-module&lt;/module&gt;
   &lt;/modules&gt;
-&lt;/project&gt;</pre></div></div></div></div>
-<div class="section">
+&lt;/project&gt;</pre></div></section></section></section><section>
 <h3><a name="Project_Inheritance_vs_Project_Aggregation">Project Inheritance vs Project Aggregation</a></h3>
 <p>If you have several Maven projects, and they all have similar configurations, you can refactor your projects by pulling out those similar configurations and making a parent project. Thus, all you have to do is to let your Maven projects inherit that parent project, and those configurations would then be applied to all of them.</p>
 <p>And if you have a group of projects that are built or processed together, you can create a parent project and have that parent project declare those projects as its modules. By doing so, you'd only have to build the parent and the rest will follow.</p>
@@ -485,10 +467,8 @@ Brett Porter" />
 <li>Specify in every child POM who their parent POM is.</li>
 <li>Change the parent POMs packaging to the value &quot;pom&quot; .</li>
 <li>Specify in the parent POM the directories of its modules (children POMs)</li></ul>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p>
-<div class="section">
-<h4><a name="Example_5">Example 5</a></h4>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p><section>
+<h4><a name="Example_5">Example 5</a></h4><section>
 <h5><a name="The_Scenario"></a>The Scenario</h5>
 <p>Given the previous original artifact POMs again,</p>
 <p><b>com.mycompany.app:my-app:1's POM</b></p>
@@ -510,8 +490,7 @@ Brett Porter" />
  |-- my-module
  |   `-- pom.xml
  `-- parent
-     `-- pom.xml</pre></div></div>
-<div class="section">
+     `-- pom.xml</pre></div></section><section>
 <h5><a name="The_Solution"></a>The Solution</h5>
 <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>
@@ -538,32 +517,28 @@ Brett Porter" />
   &lt;artifactId&gt;my-module&lt;/artifactId&gt;
 &lt;/project&gt;</pre></div>
 <p><b>NOTE:</b> Profile inheritance the same inheritance strategy as used for the POM itself.</p>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div></div></div>
-<div class="section">
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section></section></section><section>
 <h3><a name="Project_Interpolation_and_Variables"></a><a name="Project_Interpolation">Project Interpolation</a> and Variables</h3>
 <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 <tt>project.version</tt> variable, you would reference it like so:</p>
+<p>For example, to access the <code>project.version</code> variable, you would reference it like so:</p>
 <div class="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>
-<div class="section">
-<h4><a name="Available_Variables">Available Variables</a></h4>
-<div class="section">
+<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>
+<h4><a name="Available_Variables">Available Variables</a></h4><section>
 <h5><a name="Project_Model_Variables"></a>Project Model Variables</h5>
-<p>Any field of the model that is a single value element can be referenced as a variable. For example, <tt>${project.groupId}</tt>, <tt>${project.version}</tt>, <tt>${project.build.sourceDirectory}</tt> 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;<tt>project.</tt>&quot;. You may also see references with <tt>pom.</tt> as the prefix, or the prefix omitted entirely - these forms are now deprecated and should not be used.</p></div>
-<div class="section">
+<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>
 <h5><a name="Special_Variables"></a>Special Variables</h5>
 <table border="1" class="table table-striped">
 <tr class="a">
-<td align="left"><tt>project.basedir</tt></td>
+<td align="left"><code>project.basedir</code></td>
 <td align="left">The directory that the current project resides in.</td></tr>
 <tr class="b">
-<td align="left"><tt>project.baseUri</tt></td>
+<td align="left"><code>project.baseUri</code></td>
 <td align="left">The directory that the current project resides in, represented as an URI. <i>Since Maven 2.1.0</i></td></tr>
 <tr class="a">
-<td align="left"><tt>maven.build.timestamp</tt></td>
+<td align="left"><code>maven.build.timestamp</code></td>
 <td align="left">The timestamp that denotes the start of the build. <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 <tt>maven.build.timestamp.format</tt> as shown in the example below:</p>
+<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="source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;properties&gt;
@@ -571,8 +546,7 @@ Brett Porter" />
   &lt;/properties&gt;
   ...
 &lt;/project&gt;</pre></div>
-<p>The format pattern has to comply with the rules given in the API documentation for <a class="externalLink" href="http://java.sun.com/javase/6/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></div>
-<div class="section">
+<p>The format pattern has to comply with the rules given in the API documentation for <a class="externalLink" href="http://java.sun.com/javase/6/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>
 <h5><a name="Properties"></a>Properties</h5>
 <p>You are also able to reference any properties defined in the project as a variable. Consider the following example:</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
@@ -594,7 +568,7 @@ Brett Porter" />
   &lt;/dependencies&gt;
   ...
 &lt;/project&gt;</pre></div>
-<p><a href="./introduction-to-the-pom.html">[top]</a></p></div></div></div></div>
+<p><a href="./introduction-to-the-pom.html">[top]</a></p></section></section></section></section>
         </div>
       </div>
     </div>

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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/introduction/introduction-to-the-standard-directory-layout.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/introduction/introduction-to-the-standard-directory-layout.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -143,56 +143,56 @@
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Introduction_to_the_Standard_Directory_Layout"></a>Introduction to the Standard Directory Layout</h2>
 <p>Having a common directory layout would allow for 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. Please 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 border="1" class="table table-striped">
 <tr class="a">
-<td align="left"><tt>src/main/java</tt></td>
+<td align="left"><code>src/main/java</code></td>
 <td align="left">Application/Library sources</td></tr>
 <tr class="b">
-<td align="left"><tt>src/main/resources</tt></td>
+<td align="left"><code>src/main/resources</code></td>
 <td align="left">Application/Library resources</td></tr>
 <tr class="a">
-<td align="left"><tt>src/main/filters</tt></td>
+<td align="left"><code>src/main/filters</code></td>
 <td align="left">Resource filter files</td></tr>
 <tr class="b">
-<td align="left"><tt>src/main/webapp</tt></td>
+<td align="left"><code>src/main/webapp</code></td>
 <td align="left">Web application sources</td></tr>
 <tr class="a">
-<td align="left"><tt>src/test/java</tt></td>
+<td align="left"><code>src/test/java</code></td>
 <td align="left">Test sources</td></tr>
 <tr class="b">
-<td align="left"><tt>src/test/resources</tt></td>
+<td align="left"><code>src/test/resources</code></td>
 <td align="left">Test resources</td></tr>
 <tr class="a">
-<td align="left"><tt>src/test/filters</tt></td>
+<td align="left"><code>src/test/filters</code></td>
 <td align="left">Test resource filter files</td></tr>
 <tr class="b">
-<td align="left"><tt>src/it</tt></td>
+<td align="left"><code>src/it</code></td>
 <td align="left">Integration Tests (primarily for plugins)</td></tr>
 <tr class="a">
-<td align="left"><tt>src/assembly</tt></td>
+<td align="left"><code>src/assembly</code></td>
 <td align="left">Assembly descriptors</td></tr>
 <tr class="b">
-<td align="left"><tt>src/site</tt></td>
+<td align="left"><code>src/site</code></td>
 <td align="left">Site</td></tr>
 <tr class="a">
-<td align="left"><tt>LICENSE.txt</tt></td>
+<td align="left"><code>LICENSE.txt</code></td>
 <td align="left">Project's license</td></tr>
 <tr class="b">
-<td align="left"><tt>NOTICE.txt</tt></td>
+<td align="left"><code>NOTICE.txt</code></td>
 <td align="left">Notices and attributions required by libraries that the project depends on</td></tr>
 <tr class="a">
-<td align="left"><tt>README.txt</tt></td>
+<td align="left"><code>README.txt</code></td>
 <td align="left">Project's readme</td></tr></table>
-<p>At the top level, files descriptive of the project: a <tt>pom.xml</tt> file. In addition, there are textual documents meant for the user to be able to read immediately on receiving the source: <tt>README.txt</tt>, <tt>LICENSE.txt</tt>, etc.</p>
-<p>There are just two subdirectories of this structure: <tt>src</tt> and <tt>target</tt>. The only other directories that would be expected here are metadata like <tt>CVS</tt>, <tt>.git</tt> or <tt>.svn</tt>, and any subprojects in a multiproject build (each of which would be laid out as above).</p>
-<p>The <tt>target</tt> directory is used to house all output of the build.</p>
-<p>The <tt>src</tt> directory contains all of the source material for building the project, its site and so on. It contains a subdirectory for each type: <tt>main</tt> for the main build artifact, <tt>test</tt> for the unit test code and resources, <tt>site</tt> and so on.</p>
-<p>Within artifact producing source directories (ie. <tt>main</tt> and <tt>test</tt>), there is one directory for the language <tt>java</tt> (under which the normal package hierarchy exists), and one for <tt>resources</tt> (the structure which is copied to the target classpath given the default resource definition).</p>
-<p>If there are other contributing sources to the artifact build, they would be under other subdirectories: for example <tt>src/main/antlr</tt> would contain Antlr grammar definition files.</p></div>
+<p>At the top level, files descriptive of the project: a <code>pom.xml</code> file. In addition, there are textual documents meant for the user to be able to read immediately on receiving the source: <code>README.txt</code>, <code>LICENSE.txt</code>, etc.</p>
+<p>There are just two subdirectories of this structure: <code>src</code> and <code>target</code>. The only other directories that would be expected here are metadata like <code>CVS</code>, <code>.git</code> or <code>.svn</code>, and any subprojects in a multiproject build (each of which would be laid out as above).</p>
+<p>The <code>target</code> directory is used to house all output of the build.</p>
+<p>The <code>src</code> directory contains all of the source material for building the project, its site and so on. It contains a subdirectory for each type: <code>main</code> for the main build artifact, <code>test</code> for the unit test code and resources, <code>site</code> and so on.</p>
+<p>Within artifact producing source directories (ie. <code>main</code> and <code>test</code>), there is one directory for the language <code>java</code> (under which the normal package hierarchy exists), and one for <code>resources</code> (the structure which is copied to the target classpath given the default resource definition).</p>
+<p>If there are other contributing sources to the artifact build, they would be under other subdirectories: for example <code>src/main/antlr</code> would contain Antlr grammar definition files.</p></section>
         </div>
       </div>
     </div>

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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-3rd-party-jars-local.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-3rd-party-jars-local.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -144,7 +144,7 @@ Robert Scholte" />
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Guide_to_installing_3rd_party_JARs"></a>Guide to installing 3rd party JARs</h2>
 <p>Although rarely, but sometimes you will have 3rd party JARs that you need to put in your local repository for use in your builds, since they don't exist in any public repository like <a class="externalLink" href="http://search.maven.org">Maven Central</a>. The JARs must be placed in the local repository in the correct place in order for it to be correctly picked up by Apache Maven. To make this easier, and less error prone, we have provide a goal in the <a href="/plugins/maven-install-plugin/">maven-install-plugin</a> which should make this relatively painless. To install a JAR in the local repository use the following command:</p>
 <div class="source"><pre class="prettyprint linenums">
@@ -158,7 +158,7 @@ mvn install:install-file -Dfile=&lt;path
 <p>With version 2.5 of the maven-install-plugin it gets even better. If the JAR was built by Apache Maven, it'll contain a pom.xml in a subfolder of the META-INF directory, which will be read by default. In that case, all you need to do is:</p>
 <div class="source"><pre class="prettyprint linenums">
 mvn install:install-file -Dfile=&lt;path-to-file&gt;
-</pre></div></div>
+</pre></div></section>
         </div>
       </div>
     </div>

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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-3rd-party-jars-remote.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-3rd-party-jars-remote.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -143,11 +143,11 @@
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Guide_to_deploying_3rd_party_JARs_to_remote_repository"></a>Guide to deploying 3rd party JARs to remote repository</h2>
 <p>Same concept of the <a href="./guide-3rd-party-jars-local.html">install:install-file</a> goal of the maven-install-plugin where the 3rd party JAR is installed in the local repository. But this time instead to local repository the JAR will be install both in the local and remote repository.</p>
 <p>To deploy a 3rd party JAR use the deploy:deploy-file goal under maven-deploy-plugin.</p>
-<p>First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your <tt>${maven.home}/lib</tt>.</p>
+<p>First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your <code>${maven.home}/lib</code>.</p>
 <p>Then execute the command:</p>
 <div class="source"><pre class="prettyprint linenums">mvn deploy:deploy-file -DgroupId=&lt;group-id&gt; \
   -DartifactId=&lt;artifact-id&gt; \
@@ -155,22 +155,19 @@
   -Dpackaging=&lt;type-of-packaging&gt; \
   -Dfile=&lt;path-to-file&gt; \
   -DrepositoryId=&lt;id-to-map-on-server-section-of-settings.xml&gt; \
-  -Durl=&lt;url-of-the-repository-to-deploy&gt;</pre></div>
-<div class="section">
+  -Durl=&lt;url-of-the-repository-to-deploy&gt;</pre></div><section>
 <h3><a name="Deploying_a_3rd_party_JAR_with_a_generic_POM"></a>Deploying a 3rd party JAR with a generic POM</h3>
-<p>By default, deploy:deploy-file generates a generic POM(.pom) to be deploy together with the 3rd party JAR. To disable this feature we should set the <tt>generatePOM</tt> argument to false.</p>
-<div class="source"><pre class="prettyprint linenums">-DgeneratePom=false</pre></div></div>
-<div class="section">
+<p>By default, deploy:deploy-file generates a generic POM(.pom) to be deploy together with the 3rd party JAR. To disable this feature we should set the <code>generatePOM</code> argument to false.</p>
+<div class="source"><pre class="prettyprint linenums">-DgeneratePom=false</pre></div></section><section>
 <h3><a name="Deploying_a_3rd_party_JAR_with_a_customized_POM"></a>Deploying a 3rd party JAR with a customized POM</h3>
-<p>If a POM is already existing for the 3rd Party JAR and you want to deploy it together with the JAR we should use the <tt>pomFile</tt> argument of the deploy-file goal. See sample below.</p>
+<p>If a POM is already existing for the 3rd Party JAR and you want to deploy it together with the JAR we should use the <code>pomFile</code> argument of the deploy-file goal. See sample below.</p>
 <div class="source"><pre class="prettyprint linenums">mvn deploy:deploy-file -DpomFile=&lt;path-to-pom&gt; \
   -Dfile=&lt;path-to-file&gt; \
   -DrepositoryId=&lt;id-to-map-on-server-section-of-settings.xml&gt; \
   -Durl=&lt;url-of-the-repository-to-deploy&gt;</pre></div>
-<p>Note that <tt>groupId</tt>, <tt>artifactId</tt>, <tt>version</tt> and <tt>packaging</tt> arguments are not included here because deploy-file goal will get these information from the given POM.</p></div>
-<div class="section">
+<p>Note that <code>groupId</code>, <code>artifactId</code>, <code>version</code> and <code>packaging</code> arguments are not included here because deploy-file goal will get these information from the given POM.</p></section><section>
 <h3><a name="Deploying_Source_Jars"></a>Deploying Source Jars</h3>
-<p>To deploy a 3rd party source jar, packaging should be set to <tt>java-source</tt>, and generatePom should be set to <tt>false</tt>.</p></div></div>
+<p>To deploy a 3rd party source jar, packaging should be set to <code>java-source</code>, and generatePom should be set to <code>false</code>.</p></section></section>
         </div>
       </div>
     </div>

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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-archive-configuration.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-archive-configuration.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -160,12 +160,11 @@
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Guide_to_Configuring_Archive_Plugins"></a>Guide to Configuring Archive Plugins</h2>
-<p>Many Java archive generating plugins accept the <tt>archive</tt> configuration element to customize the generation of the archive. In the standard Maven Plugins, this includes the <tt>jar</tt>, <tt>war</tt>, <tt>ejb</tt>, <tt>ear</tt> and <tt>assembly</tt> plugins.</p>
-<div class="section">
+<p>Many Java archive generating plugins accept the <code>archive</code> configuration element to customize the generation of the archive. In the standard Maven Plugins, this includes the <code>jar</code>, <code>war</code>, <code>ejb</code>, <code>ear</code> and <code>assembly</code> plugins.</p><section>
 <h3><a name="Disabling_Maven_Meta_Information"></a>Disabling Maven Meta Information</h3>
-<p>By default, Maven generated archives include the <tt>META-INF/maven</tt> directory, which contains the <tt>pom.xml</tt> file used to build the archive, and a <tt>pom.properties</tt> file that includes some basic properties in a small, easier to read format.</p>
+<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="source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
@@ -185,10 +184,9 @@
   &lt;/build&gt;
   ...
 &lt;/project&gt;
-</pre></div></div>
-<div class="section">
+</pre></div></section><section>
 <h3><a name="Configuring_the_Manifest"></a>Configuring the Manifest</h3>
-<p>The archive configuration also accepts manifest configuration. See <a href="./guide-manifest.html">Guide to Working with Manifests</a> for more information.</p></div></div>
+<p>The archive configuration also accepts manifest configuration. See <a href="./guide-manifest.html">Guide to Working with Manifests</a> for more information.</p></section></section>
         </div>
       </div>
     </div>

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 Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-assemblies.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-assemblies.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -160,7 +160,7 @@
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Guide_to_creating_assemblies"></a>Guide to creating assemblies</h2>
 <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="source"><pre class="prettyprint linenums">&lt;project&gt;
@@ -196,8 +196,7 @@
   &lt;/build&gt;
   ...
 &lt;/project&gt;</pre></div>
-<p>You'll notice that the assembly descriptor is located in <tt>${project.basedir}/src/assembly</tt> which is the <a href="../introduction/introduction-to-the-standard-directory-layout.html">standard</a> location for assembly descriptors.</p>
-<div class="section">
+<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>
 <h3><a name="Creating_a_binary_assembly"></a>Creating a binary assembly</h3>
 <p>This is the most typical usage of the assembly plugin where you are creating a distribution for standard use.</p>
 <div class="source"><pre class="prettyprint linenums">&lt;assembly xmlns=&quot;http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2&quot; 
@@ -298,7 +297,7 @@
   &lt;/fileSets&gt;
 &lt;/assembly&gt;</pre></div>
 <p>You can now create the defined distribution packages via command line like this:</p>
-<div class="source"><pre class="prettyprint linenums">mvn package</pre></div></div></div>
+<div class="source"><pre class="prettyprint linenums">mvn package</pre></div></section></section>
         </div>
       </div>
     </div>

Modified: maven/website/content/guides/mini/guide-attached-tests.html
==============================================================================
--- maven/website/content/guides/mini/guide-attached-tests.html (original)
+++ maven/website/content/guides/mini/guide-attached-tests.html Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-attached-tests.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-attached-tests.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -120,9 +120,9 @@
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Guide_to_using_attached_tests"></a>Guide to using attached tests</h2>
-<p>Many times you may want to reuse the tests that you have created for a project in another. For example if you have written <tt>foo-core</tt> and it contains test code in the <tt>${basedir}/src/test/java</tt> it would be useful to package up those compiled tests in a JAR and deploy them for general reuse. To do this you would configure the <tt>maven-jar-plugin</tt> as follows:</p>
+<p>Many times you may want to reuse the tests that you have created for a project in another. For example if you have written <code>foo-core</code> and it contains test code in the <code>${basedir}/src/test/java</code> it would be useful to package up those compiled tests in a JAR and deploy them for general reuse. To do this you would configure the <code>maven-jar-plugin</code> as follows:</p>
 <div class="source"><pre class="prettyprint linenums">
 &lt;project&gt;
   &lt;build&gt;
@@ -142,22 +142,19 @@
     &lt;/plugins&gt;
   &lt;/build&gt;
 &lt;/project&gt;
-</pre></div>
-<div class="section">
+</pre></div><section>
 <h3><a name="Installing_the_attached_test_JAR"></a>Installing the attached test JAR</h3>
-<p>In order to install the attached test JAR you simply use the standard <tt>install</tt> phase by executing the following command:</p>
+<p>In order to install the attached test JAR you simply use the standard <code>install</code> phase by executing the following command:</p>
 <div class="source"><pre class="prettyprint linenums">
 mvn install
-</pre></div></div>
-<div class="section">
+</pre></div></section><section>
 <h3><a name="Deploying_the_attached_test_JAR"></a>Deploying the attached test JAR</h3>
-<p>In order to deploy the attached test JAR you simply use the standard <tt>deploy</tt> phase by executing the following command:</p>
+<p>In order to deploy the attached test JAR you simply use the standard <code>deploy</code> phase by executing the following command:</p>
 <div class="source"><pre class="prettyprint linenums">
 mvn deploy
-</pre></div></div>
-<div class="section">
+</pre></div></section><section>
 <h3><a name="Using_the_attached_test_JAR"></a>Using the attached test JAR</h3>
-<p>In order to use the attached test JAR that was created above you simply specify a dependency on the main artifact with a specified type of <tt>test-jar</tt> and the <tt>classifier</tt>.</p>
+<p>In order to use the attached test JAR that was created above you simply specify a dependency on the main artifact with a specified type of <code>test-jar</code> and the <code>classifier</code>.</p>
 <div class="source"><pre class="prettyprint linenums">
 &lt;project&gt;
   ...
@@ -173,7 +170,7 @@ mvn deploy
   &lt;/dependencies&gt;
   ...
 &lt;/project&gt;
-</pre></div></div></div>
+</pre></div></section></section>
         </div>
       </div>
     </div>

Modified: maven/website/content/guides/mini/guide-bash-m2-completion.html
==============================================================================
--- maven/website/content/guides/mini/guide-bash-m2-completion.html (original)
+++ maven/website/content/guides/mini/guide-bash-m2-completion.html Sun Jun  9 13:59:34 2019
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-bash-m2-completion.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-bash-m2-completion.apt at 2019-06-09
  | Rendered using Apache Maven Fluido Skin 1.7
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -122,9 +122,9 @@ Karl Heinz Marbaise" />
           </div>
         </div>
         <div id="bodyColumn"  class="span10" >
-<div class="section">
+<section>
 <h2><a name="Guide_to_Maven_auto_completion_using_BASH"></a>Guide to Maven auto completion using BASH</h2>
-<p>If you like having bash completion which i can recommend if you are working with Maven on command line i would suggest to install the following <a class="externalLink" href="https://github.com/juven/maven-bash-completion">Maven Bash Auto Completion</a> to fullfil you needs.</p></div>
+<p>If you like having bash completion which i can recommend if you are working with Maven on command line i would suggest to install the following <a class="externalLink" href="https://github.com/juven/maven-bash-completion">Maven Bash Auto Completion</a> to fullfil you needs.</p></section>
         </div>
       </div>
     </div>