You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2023/02/08 20:32:15 UTC
svn commit: r1907529 [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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/introduction/introduction-to-the-lifecycle.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/introduction/introduction-to-the-lifecycle.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Brett Porter" />
<meta name="date" content="2006-06-16
2015-04-04" />
@@ -147,8 +147,8 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Introduction_to_the_Build_Lifecycle"></a>Introduction to the Build Lifecycle</h1><section>
-<h2><a name="Table_Of_Contents"></a>Table Of Contents</h2>
+<h1>Introduction to the Build Lifecycle</h1><section>
+<h2>Table Of Contents</h2>
<ul>
<li><a href="#Build_Lifecycle_Basics">Build Lifecycle Basics</a></li>
<li><a href="#Setting_Up_Your_Project_to_Use_the_Build_Lifecycle">Setting Up Your Project to Use the Build Lifecycle</a>
@@ -157,11 +157,11 @@
<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></section><section>
-<h2><a name="Build_Lifecycle_Basics">Build Lifecycle Basics</a></h2>
+<h2><a id="Build_Lifecycle_Basics">Build Lifecycle Basics</a></h2>
<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 <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 web site.</p><section>
-<h3><a name="A_Build_Lifecycle_is_Made_Up_of_Phases">A Build Lifecycle is Made Up of Phases</a></h3>
+<h3><a id="A_Build_Lifecycle_is_Made_Up_of_Phases">A Build Lifecycle is Made Up of Phases</a></h3>
<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>
@@ -174,7 +174,7 @@
<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>
-<h3><a name="Usual_Command_Line_Calls">Usual Command Line Calls</a></h3>
+<h3><a id="Usual_Command_Line_Calls">Usual Command Line Calls</a></h3>
<p>You should select the phase that matches your outcome. If you want your jar, run <code>package</code>. If you want to run the unit tests, run <code>test</code>.</p>
<p>If you are uncertain what you want, the preferred phase to call is</p>
<div>
@@ -185,7 +185,7 @@
<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 <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>
-<h3><a name="A_Build_Phase_is_Made_Up_of_Plugin_Goals">A Build Phase is Made Up of Plugin Goals</a></h3>
+<h3><a id="A_Build_Phase_is_Made_Up_of_Plugin_Goals">A Build Phase is Made Up of Plugin Goals</a></h3>
<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 <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>
@@ -195,48 +195,48 @@
<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></section><section>
-<h3><a name="Some_Phases_Are_Not_Usually_Called_From_the_Command_Line">Some Phases Are Not Usually Called From the Command Line</a></h3>
+<h3><a id="Some_Phases_Are_Not_Usually_Called_From_the_Command_Line">Some Phases Are Not Usually Called From the Command Line</a></h3>
<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>
-<h2><a name="Setting_Up_Your_Project_to_Use_the_Build_Lifecycle">Setting Up Your Project to Use the Build Lifecycle</a></h2>
+<h2><a id="Setting_Up_Your_Project_to_Use_the_Build_Lifecycle">Setting Up Your Project to Use the Build Lifecycle</a></h2>
<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>
-<h3><a name="Packaging">Packaging</a></h3>
+<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><packaging></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">
+<table class="bodyTable bodyTableBorder">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>process-resources</code></td>
-<td align="left"><code>resources:resources</code></td></tr>
+<td style="text-align: left;"><code>process-resources</code></td>
+<td style="text-align: left;"><code>resources:resources</code></td></tr>
<tr class="a">
-<td align="left"><code>compile</code></td>
-<td align="left"><code>compiler:compile</code></td></tr>
+<td style="text-align: left;"><code>compile</code></td>
+<td style="text-align: left;"><code>compiler:compile</code></td></tr>
<tr class="b">
-<td align="left"><code>process-test-resources</code></td>
-<td align="left"><code>resources:testResources</code></td></tr>
+<td style="text-align: left;"><code>process-test-resources</code></td>
+<td style="text-align: left;"><code>resources:testResources</code></td></tr>
<tr class="a">
-<td align="left"><code>test-compile</code></td>
-<td align="left"><code>compiler:testCompile</code></td></tr>
+<td style="text-align: left;"><code>test-compile</code></td>
+<td style="text-align: left;"><code>compiler:testCompile</code></td></tr>
<tr class="b">
-<td align="left"><code>test</code></td>
-<td align="left"><code>surefire:test</code></td></tr>
+<td style="text-align: left;"><code>test</code></td>
+<td style="text-align: left;"><code>surefire:test</code></td></tr>
<tr class="a">
-<td align="left"><code>package</code></td>
-<td align="left"><code>jar:jar</code></td></tr>
+<td style="text-align: left;"><code>package</code></td>
+<td style="text-align: left;"><code>jar:jar</code></td></tr>
<tr class="b">
-<td align="left"><code>install</code></td>
-<td align="left"><code>install:install</code></td></tr>
+<td style="text-align: left;"><code>install</code></td>
+<td style="text-align: left;"><code>install:install</code></td></tr>
<tr class="a">
-<td align="left"><code>deploy</code></td>
-<td align="left"><code>deploy:deploy</code></td></tr></table>
+<td style="text-align: left;"><code>deploy</code></td>
+<td style="text-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><build></code> section of your POM and specify <code><extensions>true</extensions></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>
-<h3><a name="Plugins">Plugins</a></h3>
+<h3><a id="Plugins">Plugins</a></h3>
<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 <code><executions></code> element to gain more control over the order of particular goals.</p>
@@ -276,231 +276,231 @@
</executions>
</plugin></pre></div>
<p><i><a href="./introduction-to-the-lifecycle.html">[top]</a>.</i></p></section></section><section>
-<h2><a name="Lifecycle_Reference">Lifecycle Reference</a></h2>
+<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><a name="Clean_Lifecycle"></a>Clean Lifecycle</h3>
-<table border="1" class="table table-striped">
+<h3>Clean Lifecycle</h3>
+<table class="bodyTable bodyTableBorder">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">Description</th></tr>
+<th>Phase</th>
+<th>Description</th></tr>
<tr class="b">
-<td align="left"><code>pre-clean</code></td>
-<td align="left">execute processes needed prior to the actual project cleaning</td></tr>
+<td style="text-align: left;"><code>pre-clean</code></td>
+<td style="text-align: left;">execute processes needed prior to the actual project cleaning</td></tr>
<tr class="a">
-<td align="left"><code>clean</code></td>
-<td align="left">remove all files generated by the previous build</td></tr>
+<td style="text-align: left;"><code>clean</code></td>
+<td style="text-align: left;">remove all files generated by the previous build</td></tr>
<tr class="b">
-<td align="left"><code>post-clean</code></td>
-<td align="left">execute processes needed to finalize the project cleaning</td></tr></table></section><section>
-<h3><a name="Default_Lifecycle"></a>Default Lifecycle</h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">Description</th></tr>
+<th>Phase</th>
+<th>Description</th></tr>
<tr class="b">
-<td align="left"><code>validate</code></td>
-<td align="left">validate the project is correct and all necessary information is available.</td></tr>
+<td style="text-align: left;"><code>validate</code></td>
+<td style="text-align: left;">validate the project is correct and all necessary information is available.</td></tr>
<tr class="a">
-<td align="left"><code>initialize</code></td>
-<td align="left">initialize build state, e.g. set properties or create directories.</td></tr>
+<td style="text-align: left;"><code>initialize</code></td>
+<td style="text-align: left;">initialize build state, e.g. set properties or create directories.</td></tr>
<tr class="b">
-<td align="left"><code>generate-sources</code></td>
-<td align="left">generate any source code for inclusion in compilation.</td></tr>
+<td style="text-align: left;"><code>generate-sources</code></td>
+<td style="text-align: left;">generate any source code for inclusion in compilation.</td></tr>
<tr class="a">
-<td align="left"><code>process-sources</code></td>
-<td align="left">process the source code, for example to filter any values.</td></tr>
+<td style="text-align: left;"><code>process-sources</code></td>
+<td style="text-align: left;">process the source code, for example to filter any values.</td></tr>
<tr class="b">
-<td align="left"><code>generate-resources</code></td>
-<td align="left">generate resources for inclusion in the package.</td></tr>
+<td style="text-align: left;"><code>generate-resources</code></td>
+<td style="text-align: left;">generate resources for inclusion in the package.</td></tr>
<tr class="a">
-<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>
+<td style="text-align: left;"><code>process-resources</code></td>
+<td style="text-align: left;">copy and process the resources into the destination directory, ready for packaging.</td></tr>
<tr class="b">
-<td align="left"><code>compile</code></td>
-<td align="left">compile the source code of the project.</td></tr>
+<td style="text-align: left;"><code>compile</code></td>
+<td style="text-align: left;">compile the source code of the project.</td></tr>
<tr class="a">
-<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>
+<td style="text-align: left;"><code>process-classes</code></td>
+<td style="text-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"><code>generate-test-sources</code></td>
-<td align="left">generate any test source code for inclusion in compilation.</td></tr>
+<td style="text-align: left;"><code>generate-test-sources</code></td>
+<td style="text-align: left;">generate any test source code for inclusion in compilation.</td></tr>
<tr class="a">
-<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>
+<td style="text-align: left;"><code>process-test-sources</code></td>
+<td style="text-align: left;">process the test source code, for example to filter any values.</td></tr>
<tr class="b">
-<td align="left"><code>generate-test-resources</code></td>
-<td align="left">create resources for testing.</td></tr>
+<td style="text-align: left;"><code>generate-test-resources</code></td>
+<td style="text-align: left;">create resources for testing.</td></tr>
<tr class="a">
-<td align="left"><code>process-test-resources</code></td>
-<td align="left">copy and process the resources into the test destination directory.</td></tr>
+<td style="text-align: left;"><code>process-test-resources</code></td>
+<td style="text-align: left;">copy and process the resources into the test destination directory.</td></tr>
<tr class="b">
-<td align="left"><code>test-compile</code></td>
-<td align="left">compile the test source code into the test destination directory</td></tr>
+<td style="text-align: left;"><code>test-compile</code></td>
+<td style="text-align: left;">compile the test source code into the test destination directory</td></tr>
<tr class="a">
-<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.</td></tr>
+<td style="text-align: left;"><code>process-test-classes</code></td>
+<td style="text-align: left;">post-process the generated files from test compilation, for example to do bytecode enhancement on Java classes.</td></tr>
<tr class="b">
-<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>
+<td style="text-align: left;"><code>test</code></td>
+<td style="text-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"><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.</td></tr>
+<td style="text-align: left;"><code>prepare-package</code></td>
+<td style="text-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.</td></tr>
<tr class="b">
-<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>
+<td style="text-align: left;"><code>package</code></td>
+<td style="text-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"><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>
+<td style="text-align: left;"><code>pre-integration-test</code></td>
+<td style="text-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"><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>
+<td style="text-align: left;"><code>integration-test</code></td>
+<td style="text-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"><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>
+<td style="text-align: left;"><code>post-integration-test</code></td>
+<td style="text-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"><code>verify</code></td>
-<td align="left">run any checks to verify the package is valid and meets quality criteria.</td></tr>
+<td style="text-align: left;"><code>verify</code></td>
+<td style="text-align: left;">run any checks to verify the package is valid and meets quality criteria.</td></tr>
<tr class="a">
-<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>
+<td style="text-align: left;"><code>install</code></td>
+<td style="text-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"><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></section><section>
-<h3><a name="Site_Lifecycle"></a>Site Lifecycle</h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">Description</th></tr>
+<th>Phase</th>
+<th>Description</th></tr>
<tr class="b">
-<td align="left"><code>pre-site</code></td>
-<td align="left">execute processes needed prior to the actual project site generation</td></tr>
+<td style="text-align: left;"><code>pre-site</code></td>
+<td style="text-align: left;">execute processes needed prior to the actual project site generation</td></tr>
<tr class="a">
-<td align="left"><code>site</code></td>
-<td align="left">generate the project's site documentation</td></tr>
+<td style="text-align: left;"><code>site</code></td>
+<td style="text-align: left;">generate the project's site documentation</td></tr>
<tr class="b">
-<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>
+<td style="text-align: left;"><code>post-site</code></td>
+<td style="text-align: left;">execute processes needed to finalize the site generation, and to prepare for site deployment</td></tr>
<tr class="a">
-<td align="left"><code>site-deploy</code></td>
-<td align="left">deploy the generated site documentation to the specified web server</td></tr></table>
+<td style="text-align: left;"><code>site-deploy</code></td>
+<td style="text-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></section></section><section>
-<h2><a name="Built-in_Lifecycle_Bindings">Built-in Lifecycle Bindings</a></h2>
+<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><a name="Clean_Lifecycle_Bindings"></a>Clean Lifecycle Bindings</h3>
-<table border="1" class="table table-striped">
+<h3>Clean Lifecycle Bindings</h3>
+<table class="bodyTable bodyTableBorder">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>clean</code></td>
-<td align="left"><code>clean:clean</code></td></tr></table></section><section>
-<h3><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></h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>process-resources</code></td>
-<td align="left"><code>resources:resources</code></td></tr>
+<td style="text-align: left;"><code>process-resources</code></td>
+<td style="text-align: left;"><code>resources:resources</code></td></tr>
<tr class="a">
-<td align="left"><code>compile</code></td>
-<td align="left"><code>compiler:compile</code></td></tr>
+<td style="text-align: left;"><code>compile</code></td>
+<td style="text-align: left;"><code>compiler:compile</code></td></tr>
<tr class="b">
-<td align="left"><code>process-test-resources</code></td>
-<td align="left"><code>resources:testResources</code></td></tr>
+<td style="text-align: left;"><code>process-test-resources</code></td>
+<td style="text-align: left;"><code>resources:testResources</code></td></tr>
<tr class="a">
-<td align="left"><code>test-compile</code></td>
-<td align="left"><code>compiler:testCompile</code></td></tr>
+<td style="text-align: left;"><code>test-compile</code></td>
+<td style="text-align: left;"><code>compiler:testCompile</code></td></tr>
<tr class="b">
-<td align="left"><code>test</code></td>
-<td align="left"><code>surefire:test</code></td></tr>
+<td style="text-align: left;"><code>test</code></td>
+<td style="text-align: left;"><code>surefire:test</code></td></tr>
<tr class="a">
-<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>
+<td style="text-align: left;"><code>package</code></td>
+<td style="text-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"><code>install</code></td>
-<td align="left"><code>install:install</code></td></tr>
+<td style="text-align: left;"><code>install</code></td>
+<td style="text-align: left;"><code>install:install</code></td></tr>
<tr class="a">
-<td align="left"><code>deploy</code></td>
-<td align="left"><code>deploy:deploy</code></td></tr></table></section><section>
-<h3><a name="Default_Lifecycle_Bindings_-_Packaging_ear"></a>Default Lifecycle Bindings - Packaging <code>ear</code></h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>generate-resources</code></td>
-<td align="left"><code>ear:generate-application-xml</code></td></tr>
+<td style="text-align: left;"><code>generate-resources</code></td>
+<td style="text-align: left;"><code>ear:generate-application-xml</code></td></tr>
<tr class="a">
-<td align="left"><code>process-resources</code></td>
-<td align="left"><code>resources:resources</code></td></tr>
+<td style="text-align: left;"><code>process-resources</code></td>
+<td style="text-align: left;"><code>resources:resources</code></td></tr>
<tr class="b">
-<td align="left"><code>package</code></td>
-<td align="left"><code>ear:ear</code></td></tr>
+<td style="text-align: left;"><code>package</code></td>
+<td style="text-align: left;"><code>ear:ear</code></td></tr>
<tr class="a">
-<td align="left"><code>install</code></td>
-<td align="left"><code>install:install</code></td></tr>
+<td style="text-align: left;"><code>install</code></td>
+<td style="text-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>
-<h3><a name="Default_Lifecycle_Bindings_-_Packaging_maven-plugin"></a>Default Lifecycle Bindings - Packaging <code>maven-plugin</code></h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>generate-resources</code></td>
-<td align="left"><code>plugin:descriptor</code></td></tr>
+<td style="text-align: left;"><code>generate-resources</code></td>
+<td style="text-align: left;"><code>plugin:descriptor</code></td></tr>
<tr class="a">
-<td align="left"><code>process-resources</code></td>
-<td align="left"><code>resources:resources</code></td></tr>
+<td style="text-align: left;"><code>process-resources</code></td>
+<td style="text-align: left;"><code>resources:resources</code></td></tr>
<tr class="b">
-<td align="left"><code>compile</code></td>
-<td align="left"><code>compiler:compile</code></td></tr>
+<td style="text-align: left;"><code>compile</code></td>
+<td style="text-align: left;"><code>compiler:compile</code></td></tr>
<tr class="a">
-<td align="left"><code>process-test-resources</code></td>
-<td align="left"><code>resources:testResources</code></td></tr>
+<td style="text-align: left;"><code>process-test-resources</code></td>
+<td style="text-align: left;"><code>resources:testResources</code></td></tr>
<tr class="b">
-<td align="left"><code>test-compile</code></td>
-<td align="left"><code>compiler:testCompile</code></td></tr>
+<td style="text-align: left;"><code>test-compile</code></td>
+<td style="text-align: left;"><code>compiler:testCompile</code></td></tr>
<tr class="a">
-<td align="left"><code>test</code></td>
-<td align="left"><code>surefire:test</code></td></tr>
+<td style="text-align: left;"><code>test</code></td>
+<td style="text-align: left;"><code>surefire:test</code></td></tr>
<tr class="b">
-<td align="left"><code>package</code></td>
-<td align="left"><code>jar:jar</code> <i>and</i> <code>plugin:addPluginArtifactMetadata</code></td></tr>
+<td style="text-align: left;"><code>package</code></td>
+<td style="text-align: left;"><code>jar:jar</code> <i>and</i> <code>plugin:addPluginArtifactMetadata</code></td></tr>
<tr class="a">
-<td align="left"><code>install</code></td>
-<td align="left"><code>install:install</code></td></tr>
+<td style="text-align: left;"><code>install</code></td>
+<td style="text-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>
-<h3><a name="Default_Lifecycle_Bindings_-_Packaging_pom"></a>Default Lifecycle Bindings - Packaging <code>pom</code></h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>package</code></td>
-<td align="left"></td></tr>
+<td style="text-align: left;"><code>package</code></td>
+<td style="text-align: left;"></td></tr>
<tr class="a">
-<td align="left"><code>install</code></td>
-<td align="left"><code>install:install</code></td></tr>
+<td style="text-align: left;"><code>install</code></td>
+<td style="text-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>
-<h3><a name="Site_Lifecycle_Bindings"></a>Site Lifecycle Bindings</h3>
-<table border="1" class="table table-striped">
+<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">
<tr class="a">
-<th align="left">Phase</th>
-<th align="left">plugin:goal</th></tr>
+<th>Phase</th>
+<th>plugin:goal</th></tr>
<tr class="b">
-<td align="left"><code>site</code></td>
-<td align="left"><code>site:site</code></td></tr>
+<td style="text-align: left;"><code>site</code></td>
+<td style="text-align: left;"><code>site:site</code></td></tr>
<tr class="a">
-<td align="left"><code>site-deploy</code></td>
-<td align="left"><code>site:deploy</code></td></tr></table></section><section>
-<h3><a name="References"></a>References</h3>
+<td style="text-align: left;"><code>site-deploy</code></td>
+<td style="text-align: left;"><code>site:deploy</code></td></tr></table></section><section>
+<h3>References</h3>
<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>
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/introduction/introduction-to-the-pom.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/introduction/introduction-to-the-pom.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Jason van Zyl
Franz Allan Valencia See
Brett Porter" />
@@ -148,7 +148,7 @@ Brett Porter" />
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Introduction_to_the_POM"></a>Introduction to the POM</h1>
+<h1>Introduction to the POM</h1>
<ul>
<li><a href="./introduction-to-the-pom.html#What_is_a_POM">What is a POM</a>?</li>
<li><a href="./introduction-to-the-pom.html#Super_POM">Super POM</a></li>
@@ -167,15 +167,15 @@ Brett Porter" />
<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><section>
-<h2><a name="What_is_a_POM.3F"></a><a name="What_is_a_POM">What is a POM</a>?</h2>
+<h2><a id="What_is_a_POM">What is a POM</a>?</h2>
<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></section><section>
-<h2><a name="Super_POM">Super POM</a></h2>
+<h2><a id="Super_POM">Super POM</a></h2>
<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.</p>
<p>You can see the <a href="/ref/3.6.3/maven-model-builder/super-pom.html">Super POM for Maven 3.6.3</a> in Maven Core reference documentation.</p>
<p><a href="./introduction-to-the-pom.html">[top]</a></p></section><section>
-<h2><a name="Minimal_POM">Minimal POM</a></h2>
+<h2><a id="Minimal_POM">Minimal POM</a></h2>
<p>The minimum requirement for a POM are the following:</p>
<ul>
<li><code>project</code> root</li>
@@ -195,7 +195,7 @@ Brett Porter" />
<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 "jar" 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 <code>https://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>
-<h2><a name="Project_Inheritance">Project Inheritance</a></h2>
+<h2><a id="Project_Inheritance">Project Inheritance</a></h2>
<p>Elements in the POM that are merged are the following:</p>
<ul>
<li>dependencies</li>
@@ -205,8 +205,8 @@ Brett Porter" />
<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><section>
-<h3><a name="Example_1">Example 1</a></h3><section>
-<h4><a name="The_Scenario"></a>The Scenario</h4>
+<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="source"><pre class="prettyprint linenums"><project>
<modelVersion>4.0.0</modelVersion>
@@ -222,7 +222,7 @@ Brett Porter" />
| `-- pom.xml
`-- pom.xml</pre></div>
<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>
-<h4><a name="The_Solution"></a>The Solution</h4>
+<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="source"><pre class="prettyprint linenums"><project>
@@ -253,8 +253,8 @@ Brett Porter" />
</project></pre></div>
<p>This allows the module to inherit the groupId or the version of its parent POM.</p>
<p><a href="./introduction-to-the-pom.html">[top]</a></p></section></section><section>
-<h3><a name="Example_2">Example 2</a></h3><section>
-<h4><a name="The_Scenario"></a>The Scenario</h4>
+<h3><a id="Example_2">Example 2</a></h3><section>
+<h4>The Scenario</h4>
<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>
@@ -263,7 +263,7 @@ Brett Porter" />
| `-- pom.xml
`-- parent
`-- pom.xml</pre></div></section><section>
-<h4><a name="The_Solution"></a>The Solution</h4>
+<h4>The Solution</h4>
<p>To address this directory structure (or any other directory structure), we would have to add the <code><relativePath></code> element to our parent section.</p>
<div class="source"><pre class="prettyprint linenums"><project>
<modelVersion>4.0.0</modelVersion>
@@ -278,14 +278,14 @@ Brett Porter" />
<artifactId>my-module</artifactId>
</project></pre></div>
<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>
-<h2><a name="Project_Aggregation">Project Aggregation</a></h2>
+<h2><a id="Project_Aggregation">Project Aggregation</a></h2>
<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 "pom".</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><section>
-<h3><a name="Example_3">Example 3</a></h3><section>
-<h4><a name="The_Scenario"></a>The Scenario</h4>
+<h3><a id="Example_3">Example 3</a></h3><section>
+<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="source"><pre class="prettyprint linenums"><project>
@@ -309,7 +309,7 @@ Brett Porter" />
|-- my-module
| `-- pom.xml
`-- pom.xml</pre></div></section><section>
-<h4><a name="The_Solution"></a>The Solution</h4>
+<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="source"><pre class="prettyprint linenums"><project>
<modelVersion>4.0.0</modelVersion>
@@ -326,8 +326,8 @@ Brett Porter" />
<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 "pom", and for the modules section, we have the element <code><module>my-module</module></code>. The value of <code><module></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></section></section><section>
-<h3><a name="Example_4">Example 4</a></h3><section>
-<h4><a name="The_Scenario"></a>The Scenario</h4>
+<h3><a id="Example_4">Example 4</a></h3><section>
+<h4>The Scenario</h4>
<p>But what if we change the directory structure to the following:</p>
<div>
<pre>.
@@ -336,7 +336,7 @@ Brett Porter" />
`-- parent
`-- pom.xml</pre></div>
<p>How would the parent POM specify its modules?</p></section><section>
-<h4><a name="The_Solution"></a>The Solution</h4>
+<h4>The Solution</h4>
<p>The answer? - the same way as Example 3, by specifying the path to the module.</p>
<div class="source"><pre class="prettyprint linenums"><project>
<modelVersion>4.0.0</modelVersion>
@@ -350,7 +350,7 @@ Brett Porter" />
<module>../my-module</module>
</modules>
</project></pre></div></section></section></section><section>
-<h2><a name="Project_Inheritance_vs_Project_Aggregation">Project Inheritance vs Project Aggregation</a></h2>
+<h2><a id="Project_Inheritance_vs_Project_Aggregation">Project Inheritance vs Project Aggregation</a></h2>
<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>
<p>But of course, you can have both Project Inheritance and Project Aggregation. Meaning, you can have your modules specify a parent project, and at the same time, have that parent project specify those Maven projects as its modules. You'd just have to apply all three rules:</p>
@@ -359,8 +359,8 @@ Brett Porter" />
<li>Change the parent POMs packaging to the value "pom" .</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><section>
-<h3><a name="Example_5">Example 5</a></h3><section>
-<h4><a name="The_Scenario"></a>The Scenario</h4>
+<h3><a id="Example_5">Example 5</a></h3><section>
+<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="source"><pre class="prettyprint linenums"><project>
@@ -385,7 +385,7 @@ Brett Porter" />
| `-- pom.xml
`-- parent
`-- pom.xml</pre></div></section><section>
-<h4><a name="The_Solution"></a>The Solution</h4>
+<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="source"><pre class="prettyprint linenums"><project>
@@ -415,26 +415,26 @@ Brett Porter" />
</project></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></section></section></section><section>
-<h2><a name="Project_Interpolation_and_Variables"></a><a name="Project_Interpolation">Project Interpolation</a> and Variables</h2>
+<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="source"><pre class="prettyprint linenums"> <version>${project.version}</version></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 name="Available_Variables">Available Variables</a></h3><section>
-<h4><a name="Project_Model_Variables"></a>Project Model Variables</h4>
+<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 "<code>project.</code>". 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><a name="Special_Variables"></a>Special Variables</h4>
-<table border="1" class="table table-striped">
+<h4>Special Variables</h4>
+<table class="bodyTable bodyTableBorder">
<tr class="a">
-<td align="left"><code>project.basedir</code></td>
-<td align="left">The directory that the current project resides in.</td></tr>
+<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>
<tr class="b">
-<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>
+<td style="text-align: left;"><code>project.baseUri</code></td>
+<td style="text-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"><code>maven.build.timestamp</code></td>
-<td align="left">The timestamp that denotes the start of the build (UTC). <i>Since Maven 2.1.0-M1</i></td></tr></table>
+<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="source"><pre class="prettyprint linenums"><project>
...
@@ -444,7 +444,7 @@ Brett Porter" />
...
</project></pre></div>
<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><a name="Properties"></a>Properties</h4>
+<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="source"><pre class="prettyprint linenums"><project>
...
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/introduction/introduction-to-the-standard-directory-layout.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/introduction/introduction-to-the-standard-directory-layout.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Jason van Zyl" />
<meta name="date" content="2014-03-09" />
<title>Maven – Introduction to the Standard Directory Layout</title>
@@ -146,49 +146,49 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Introduction_to_the_Standard_Directory_Layout"></a>Introduction to the Standard Directory Layout</h1>
+<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 border="1" class="table table-striped">
+<table class="bodyTable bodyTableBorder">
<tr class="a">
-<td align="left"><code>src/main/java</code></td>
-<td align="left">Application/Library sources</td></tr>
+<td style="text-align: left;"><code>src/main/java</code></td>
+<td style="text-align: left;">Application/Library sources</td></tr>
<tr class="b">
-<td align="left"><code>src/main/resources</code></td>
-<td align="left">Application/Library resources</td></tr>
+<td style="text-align: left;"><code>src/main/resources</code></td>
+<td style="text-align: left;">Application/Library resources</td></tr>
<tr class="a">
-<td align="left"><code>src/main/filters</code></td>
-<td align="left">Resource filter files</td></tr>
+<td style="text-align: left;"><code>src/main/filters</code></td>
+<td style="text-align: left;">Resource filter files</td></tr>
<tr class="b">
-<td align="left"><code>src/main/webapp</code></td>
-<td align="left">Web application sources</td></tr>
+<td style="text-align: left;"><code>src/main/webapp</code></td>
+<td style="text-align: left;">Web application sources</td></tr>
<tr class="a">
-<td align="left"><code>src/test/java</code></td>
-<td align="left">Test sources</td></tr>
+<td style="text-align: left;"><code>src/test/java</code></td>
+<td style="text-align: left;">Test sources</td></tr>
<tr class="b">
-<td align="left"><code>src/test/resources</code></td>
-<td align="left">Test resources</td></tr>
+<td style="text-align: left;"><code>src/test/resources</code></td>
+<td style="text-align: left;">Test resources</td></tr>
<tr class="a">
-<td align="left"><code>src/test/filters</code></td>
-<td align="left">Test resource filter files</td></tr>
+<td style="text-align: left;"><code>src/test/filters</code></td>
+<td style="text-align: left;">Test resource filter files</td></tr>
<tr class="b">
-<td align="left"><code>src/it</code></td>
-<td align="left">Integration Tests (primarily for plugins)</td></tr>
+<td style="text-align: left;"><code>src/it</code></td>
+<td style="text-align: left;">Integration Tests (primarily for plugins)</td></tr>
<tr class="a">
-<td align="left"><code>src/assembly</code></td>
-<td align="left">Assembly descriptors</td></tr>
+<td style="text-align: left;"><code>src/assembly</code></td>
+<td style="text-align: left;">Assembly descriptors</td></tr>
<tr class="b">
-<td align="left"><code>src/site</code></td>
-<td align="left">Site</td></tr>
+<td style="text-align: left;"><code>src/site</code></td>
+<td style="text-align: left;">Site</td></tr>
<tr class="a">
-<td align="left"><code>LICENSE.txt</code></td>
-<td align="left">Project's license</td></tr>
+<td style="text-align: left;"><code>LICENSE.txt</code></td>
+<td style="text-align: left;">Project's license</td></tr>
<tr class="b">
-<td align="left"><code>NOTICE.txt</code></td>
-<td align="left">Notices and attributions required by libraries that the project depends on</td></tr>
+<td style="text-align: left;"><code>NOTICE.txt</code></td>
+<td style="text-align: left;">Notices and attributions required by libraries that the project depends on</td></tr>
<tr class="a">
-<td align="left"><code>README.txt</code></td>
-<td align="left">Project's readme</td></tr></table>
+<td style="text-align: left;"><code>README.txt</code></td>
+<td style="text-align: left;">Project's readme</td></tr></table>
<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>
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-3rd-party-jars-local.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-3rd-party-jars-local.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Jason van Zyl
Robert Scholte" />
<meta name="date" content="2013-07-13" />
@@ -154,7 +154,7 @@ Robert Scholte" />
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_installing_3rd_party_JARs"></a>Guide to installing 3rd party JARs</h1>
+<h1>Guide to installing 3rd party JARs</h1>
<p>Occasionally, 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="https://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.</p>
<p>To make this easier, and less error prone, we have provided an <code>install-file</code> goal in the <a href="/plugins/maven-install-plugin/">maven-install-plugin</a> which should make this relatively painless. </p>
<p>To install a JAR in the local repository use the following command:</p>
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-3rd-party-jars-remote.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-3rd-party-jars-remote.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Allan Ramirez" />
<meta name="date" content="2006-02-22" />
<title>Maven – Guide to deploying 3rd party JARs to remote repository</title>
@@ -153,7 +153,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_deploying_3rd_party_JARs_to_remote_repository"></a>Guide to deploying 3rd party JARs to remote repository</h1>
+<h1>Guide to deploying 3rd party JARs to remote repository</h1>
<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 <code>${maven.home}/lib</code>.</p>
@@ -166,11 +166,11 @@
-Dfile=<path-to-file> \
-DrepositoryId=<id-to-map-on-server-section-of-settings.xml> \
-Durl=<url-of-the-repository-to-deploy></pre></div><section>
-<h2><a name="Deploying_a_3rd_party_JAR_with_a_generic_POM"></a>Deploying a 3rd party JAR with a generic POM</h2>
+<h2>Deploying a 3rd party JAR with a generic POM</h2>
<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>
<pre>-DgeneratePom=false</pre></div></section><section>
-<h2><a name="Deploying_a_3rd_party_JAR_with_a_customized_POM"></a>Deploying a 3rd party JAR with a customized POM</h2>
+<h2>Deploying a 3rd party JAR with a customized POM</h2>
<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>
<pre>mvn deploy:deploy-file -DpomFile=<path-to-pom> \
@@ -178,7 +178,7 @@
-DrepositoryId=<id-to-map-on-server-section-of-settings.xml> \
-Durl=<url-of-the-repository-to-deploy></pre></div>
<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>
-<h2><a name="Deploying_Source_Jars"></a>Deploying Source Jars</h2>
+<h2>Deploying Source Jars</h2>
<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>
</main>
</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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-archive-configuration.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-archive-configuration.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Brett Porter" />
<meta name="date" content="2006-06-21" />
<title>Maven – Guide to Configuring Archive Plugins</title>
@@ -155,9 +155,9 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_Configuring_Archive_Plugins"></a>Guide to Configuring Archive Plugins</h1>
+<h1>Guide to Configuring Archive Plugins</h1>
<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>
-<h2><a name="Disabling_Maven_Meta_Information"></a>Disabling Maven Meta Information</h2>
+<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="source"><pre class="prettyprint linenums"><project>
@@ -179,7 +179,7 @@
...
</project>
</pre></div></section><section>
-<h2><a name="Configuring_the_Manifest"></a>Configuring the Manifest</h2>
+<h2>Configuring the Manifest</h2>
<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>
</main>
</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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-assemblies.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-assemblies.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Jason van Zyl" />
<meta name="date" content="2005-10-12" />
<title>Maven – Guide to Creating Assemblies</title>
@@ -155,7 +155,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_creating_assemblies"></a>Guide to creating assemblies</h1>
+<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="source"><pre class="prettyprint linenums"><project>
<parent>
@@ -193,7 +193,7 @@
...
</project></pre></div>
<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><a name="Creating_a_binary_assembly"></a>Creating a binary assembly</h2>
+<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="source"><pre class="prettyprint linenums"><assembly xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd">
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-attached-tests.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-attached-tests.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Jason van Zyl" />
<meta name="date" content="2005-10-12" />
<title>Maven – Guide to using attached tests</title>
@@ -124,7 +124,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_using_attached_tests"></a>Guide to using attached tests</h1>
+<h1>Guide to using attached tests</h1>
<p>You can reuse the tests that you have created for one project in another. For example, suppose <code>foo-core</code> contains test code in the <code>${basedir}/src/test/java</code>. To package up those compiled tests in a JAR and deploy them for general reuse, configure the <code>maven-jar-plugin</code> as follows:</p>
<div class="source"><pre class="prettyprint linenums">
<project>
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-bash-m2-completion.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-bash-m2-completion.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Trygve Laugstol
Jason van Zyl
Karl Heinz Marbaise" />
@@ -126,7 +126,7 @@ Karl Heinz Marbaise" />
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_Maven_auto_completion_using_BASH"></a>Guide to Maven auto completion using BASH</h1>
+<h1>Guide to Maven auto completion using BASH</h1>
<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>
</main>
</div>
Modified: maven/website/content/guides/mini/guide-building-for-different-environments.html
==============================================================================
--- maven/website/content/guides/mini/guide-building-for-different-environments.html (original)
+++ maven/website/content/guides/mini/guide-building-for-different-environments.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-building-for-different-environments.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-building-for-different-environments.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Trygve Laugstøl" />
<meta name="date" content="2006-01-01" />
<title>Maven – Building For Different Environments</title>
@@ -155,7 +155,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Building_For_Different_Environments"></a>Building For Different Environments</h1>
+<h1>Building For Different Environments</h1>
<p>Building the same artifact for different environments has always been an annoyance. You have multiple environments, for instance test and production servers or, maybe a set of servers that run the same application with different configurations. In this guide I'll explain how you can use profiles to build and package artifacts configured for specific environments. See <a href="../introduction/introduction-to-profiles.html">Introduction to Build Profiles</a> for a more in-depth explanation of the profile concept.</p>
<p>Note:</p>
<ul>
@@ -232,13 +232,13 @@ src/
<li>It will configure the test plugin to skip all tests when building the test and production artifacts. This is useful as you probably don't want to run tests against the production system</li>
<li>It configures the JAR plugin to create an "attached" JAR with the "test" classifier.
<p>To activate this profile execute <code>mvn -Ptest install</code> and Maven will execute the steps in the profile in addition to the normal steps. From this build you will get two artifacts, "foo-1.0.jar" and "foo-1.0-test.jar". These two jars will identical. </p></li></ol></li></ul></section><section>
-<h1><a name="Caveats"></a>Caveats</h1>
+<h1>Caveats</h1>
<ul>
<li>Currently Maven doesn't allow a project build to only produce attached artifacts. (i.e. it has to produce a "main" artifact as well) This results in two equal JARs being packaged and installed. The JAR plugin probably should also get improved support for this use case to that two different output directories will be used as the basis for building the JAR.</li>
<li>The usage of the delete task might seem a bit odd but is required to make sure that the copy task actually will copy the file. The copy task will look at the timestamps of the source and destination files, only when copying the files it won't know that the actually source file might be different than the last time it was executed.</li>
<li>After the build the test configuration will be in target/classes and won't be overridden because the resources plugin uses the same timestamp checking, so you should always do a clean after executing Maven with a profile.</li>
<li>For the reasons given above it's imperative that you only build an artifact for a single environment in a single execution at a time and that you execute "mvn clean" whenever you change the profile switches. If not, you might get artifacts with a mixed set of configuration files.</li></ul></section><section>
-<h1><a name="Resources"></a>Resources</h1>
+<h1>Resources</h1>
<ol style="list-style-type: decimal">
<li><a href="../introduction/introduction-to-profiles.html">Introduction to Build Profiles</a></li>
<li><a href="../introduction/introduction-to-the-standard-directory-layout.html">Standard Directory Layout</a></li></ol></section>
Modified: maven/website/content/guides/mini/guide-configuring-maven.html
==============================================================================
--- maven/website/content/guides/mini/guide-configuring-maven.html (original)
+++ maven/website/content/guides/mini/guide-configuring-maven.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/guides/mini/guide-configuring-maven.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/guides/mini/guide-configuring-maven.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Brett Porter" />
<meta name="date" content="2005-04-12" />
<title>Maven – Guide to Configuring Maven</title>
@@ -155,7 +155,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Configuring_Maven"></a>Configuring Maven</h1>
+<h1>Configuring Maven</h1>
<p>Maven configuration occurs at 3 levels:</p>
<ul>
<li><i>Project</i> - most static configuration occurs in <code>pom.xml</code></li>
@@ -165,7 +165,7 @@
<p><b>Note:</b> the installation and user configuration cannot be used to add shared project information - for example, setting <code><organization></code> or <code><distributionManagement></code> company-wide.</p>
<p>For this, you should have your projects inherit from a company-wide parent <code>pom.xml</code>.</p>
<p>You can specify your user configuration in <code>${user.home}/.m2/settings.xml</code>. A <a href="../../maven-settings/settings.html">full reference</a> to the configuration file is available. This section will show how to make some common configurations. Note that the file is not required - defaults will be used if it is not found.</p><section>
-<h2><a name="Configuring_your_Local_Repository"></a>Configuring your Local Repository</h2>
+<h2>Configuring your Local Repository</h2>
<p>The location of your local repository can be changed in your user configuration. The default value is <code>${user.home}/.m2/repository/</code>.</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
@@ -173,17 +173,17 @@
...
</settings></pre></div>
<p><b>Note:</b> The local repository must be an absolute path.</p></section><section>
-<h2><a name="Configuring_a_Proxy"></a>Configuring a Proxy</h2>
+<h2>Configuring a Proxy</h2>
<p>Proxy configuration can also be specified in the settings file.</p>
<p>For more information, see the <a href="./guide-proxies.html"> Guide to using a Proxy</a>.</p></section><section>
-<h2><a name="Configuring_Parallel_Artifact_Resolution"></a>Configuring Parallel Artifact Resolution</h2>
+<h2>Configuring Parallel Artifact Resolution</h2>
<p>By default, Maven 2.1.0+ will download up to 5 artifacts (from different groups) at once. To change the size of the thread pool, start Maven using <code>-Dmaven.artifact.threads</code>. For example, to only download single artifacts at a time:</p>
<div>
<pre>mvn -Dmaven.artifact.threads=1 verify</pre></div>
<p>You may wish to set this option permanently, in which case you can use the <code>MAVEN_OPTS</code> environment variable. For example:</p>
<div>
<pre>export MAVEN_OPTS=-Dmaven.artifact.threads=3</pre></div></section><section>
-<h2><a name="Security_and_Deployment_Settings"></a>Security and Deployment Settings</h2>
+<h2>Security and Deployment Settings</h2>
<p>Repositories to deploy to are defined in a project in the <code><distributionManagement></code> section. However, you cannot put your username, password, or other security settings in that project. For that reason, you should add a server definition to your own settings with an <code>id</code> that matches that of the deployment repository in the project.</p>
<p>In addition, some repositories may require authorization to download from, so the corresponding settings can be specified in a <code>server</code> element in the same way.</p>
<p>Which settings are required will depend on the type of repository you are deploying to. As of the first release, only SCP deployments and file deployments are supported by default, so only the following SCP configuration is needed:</p>
@@ -204,13 +204,13 @@
...
</settings></pre></div>
<p>To encrypt passwords in these sections, refer to <a href="./guide-encryption.html"> Encryption Settings</a>.</p></section><section>
-<h2><a name="Using_Mirrors_for_Repositories"></a>Using Mirrors for Repositories</h2>
+<h2>Using Mirrors for Repositories</h2>
<p>Repositories can be declared inside a project, which means that if you have your own custom repositories, those sharing your project easily get the right settings out of the box. However, you may want to use an alternative mirror for a particular repository without changing the project files. Refer to <a href="./guide-mirror-settings.html"> Guide to Mirror Settings</a> for more details.</p></section><section>
-<h2><a name="Profiles"></a>Profiles</h2>
+<h2>Profiles</h2>
<p>Repository configuration can also be put into a profile. You can have multiple profiles, with one set to active so that you can easily switch environments. Read more about profiles in <a href="../introduction/introduction-to-profiles.html">Introduction to Build Profiles</a>.</p></section><section>
-<h2><a name="Optional_configuration"></a>Optional configuration</h2>
+<h2>Optional configuration</h2>
<p>Maven will work for most tasks with the above configuration, however if you have any environmental specific configuration outside of individual projects then you will need to configure settings. The following sections refer to what is available.</p><section>
-<h3><a name="Settings"></a>Settings</h3>
+<h3>Settings</h3>
<p>Maven has a settings file located in the Maven installation and/or user home directory that configure environmental specifics such as:</p>
<ul>
<li>HTTP proxy server</li>
@@ -218,9 +218,9 @@
<li>server authentication and passwords</li>
<li>other configuration properties</li></ul>
<p>For information on this file, see the <a href="/settings.html">Settings reference</a></p></section><section>
-<h3><a name="Security"></a>Security</h3>
+<h3>Security</h3>
<p>As of Maven 2.1.0+, you can encrypt passwords in your settings file, however you must first configure a master password. For more information on both server passwords and the master password, see the <a href="./guide-encryption.html">Guide to Password Encryption</a>.</p></section><section>
-<h3><a name="Toolchains"></a>Toolchains</h3>
+<h3>Toolchains</h3>
<p>As of Maven 2.0.9+, you can build a project using a specific version of JDK independent from the one Maven is running with. For more information, see the <a href="./guide-using-toolchains.html">Guide to Using Toolchains</a>.</p></section></section></section>
</main>
</div>