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 [8/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/ doc...
Modified: maven/website/content/guides/getting-started/index.html
==============================================================================
--- maven/website/content/guides/getting-started/index.html (original)
+++ maven/website/content/guides/getting-started/index.html 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/getting-started/index.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/getting-started/index.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,11 +144,10 @@ Vincent Siveton" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Maven_Getting_Started_Guide"></a>Maven Getting Started Guide</h2>
<p>This guide is intended as a reference for those working with Maven for the first time, but is also intended to serve as a cookbook with self-contained references and solutions for common use cases. For first time users, it is recommended that you step through the material in a sequential fashion. For users more familiar with Maven, this guide endeavours to provide a quick solution for the need at hand. It is assumed at this point that you have downloaded Maven and installed Maven on your local machine. If you have not done so please refer to the <a href="../../download.html">Download and Installation</a> instructions.</p>
-<p>Ok, so you now have Maven installed and we're ready to go. Before we jump into our examples we'll very briefly go over what Maven is and how it can help you with your daily work and collaborative efforts with team members. Maven will, of course, work for small projects, but Maven shines in helping teams operate more effectively by allowing team members to focus on what the stakeholders of a project require. You can leave the build infrastructure to Maven!</p></div>
-<div class="section">
+<p>Ok, so you now have Maven installed and we're ready to go. Before we jump into our examples we'll very briefly go over what Maven is and how it can help you with your daily work and collaborative efforts with team members. Maven will, of course, work for small projects, but Maven shines in helping teams operate more effectively by allowing team members to focus on what the stakeholders of a project require. You can leave the build infrastructure to Maven!</p></section><section>
<h2><a name="Sections"></a>Sections</h2>
<ul>
<li><a href="./index.html#What_is_Maven">What is Maven?</a></li>
@@ -166,8 +165,7 @@ Vincent Siveton" />
<li><a href="./index.html#How_do_I_deploy_my_jar_in_my_remote_repository">How do I deploy my jar in my remote repository?</a></li>
<li><a href="./index.html#How_do_I_create_documentation">How do I create documentation?</a></li>
<li><a href="./index.html#How_do_I_build_other_types_of_projects">How do I build other types of projects?</a></li>
-<li><a href="./index.html#How_do_I_build_more_than_one_project_at_once">How do I build more than one project at once?</a></li></ul>
-<div class="section">
+<li><a href="./index.html#How_do_I_build_more_than_one_project_at_once">How do I build more than one project at once?</a></li></ul><section>
<h3><a name="What_is_Maven.3F"></a><a name="What_is_Maven">What is Maven?</a></h3>
<p>At first glance Maven can appear to be many things, but in a nutshell Maven is an attempt <i>to apply patterns to a project's build infrastructure in order to promote comprehension and productivity by providing a clear path in the use of best practices</i>. Maven is essentially a project management and comprehension tool and as such provides a way to help with managing:</p>
<ul>
@@ -178,15 +176,12 @@ Vincent Siveton" />
<li>SCMs</li>
<li>Releases</li>
<li>Distribution</li></ul>
-<p>If you want more background information on Maven you can check out <a href="../../background/philosophy-of-maven.html">The Philosophy of Maven</a> and <a href="../../background/history-of-maven.html">The History of Maven</a>. Now let's move on to how you, the user, can benefit from using Maven.</p></div>
-<div class="section">
+<p>If you want more background information on Maven you can check out <a href="../../background/philosophy-of-maven.html">The Philosophy of Maven</a> and <a href="../../background/history-of-maven.html">The History of Maven</a>. Now let's move on to how you, the user, can benefit from using Maven.</p></section><section>
<h3><a name="How_can_Maven_benefit_my_development_process.3F"></a><a name="How_can_Maven_benefit_my_development_process">How can Maven benefit my development process?</a></h3>
<p>Maven can provide benefits for your build process by employing standard conventions and practices to accelerate your development cycle while at the same time helping you achieve a higher rate of success.</p>
-<p>Now that we have covered a little bit of the history and purpose of Maven let's get into some real examples to get you up and running with Maven!</p></div>
-<div class="section">
+<p>Now that we have covered a little bit of the history and purpose of Maven let's get into some real examples to get you up and running with Maven!</p></section><section>
<h3><a name="How_do_I_setup_Maven.3F"></a><a name="How_do_I_setup_Maven">How do I setup Maven?</a></h3>
-<p>The defaults for Maven are often sufficient, but if you need to change the cache location or are behind a HTTP proxy, you will need to create configuration. See the <a href="../mini/guide-configuring-maven.html"> Guide to Configuring Maven</a> for more information.</p></div>
-<div class="section">
+<p>The defaults for Maven are often sufficient, but if you need to change the cache location or are behind a HTTP proxy, you will need to create configuration. See the <a href="../mini/guide-configuring-maven.html"> Guide to Configuring Maven</a> for more information.</p></section><section>
<h3><a name="How_do_I_make_my_first_Maven_project.3F"></a><a name="How_do_I_make_my_first_Maven_project">How do I make my first Maven project?</a></h3>
<p>We are going to jump headlong into creating your first Maven project! To create our first Maven project we are going to use Maven's archetype mechanism. An archetype is defined as <i>an original pattern or model from which all other things of the same kind are made</i>. In Maven, an archetype is a template of a project which is combined with some user input to produce a working Maven project that has been tailored to the user's requirements. We are going to show you how the archetype mechanism works now, but if you would like to know more about archetypes please refer to our <a href="../introduction/introduction-to-archetypes.html">Introduction to Archetypes</a>.</p>
<p>On to creating your first project! In order to create the simplest of Maven projects, execute the following from the command line:</p>
@@ -194,7 +189,7 @@ Vincent Siveton" />
-DarchetypeGroupId=org.apache.maven.archetypes \
-DgroupId=com.mycompany.app \
-DartifactId=my-app</pre></div>
-<p>Once you have executed this command, you will notice a few things have happened. First, you will notice that a directory named <tt>my-app</tt> has been created for the new project, and this directory contains a file named <tt>pom.xml</tt> that should look like this:</p>
+<p>Once you have executed this command, you will notice a few things have happened. First, you will notice that a directory named <code>my-app</code> has been created for the new project, and this directory contains a file named <code>pom.xml</code> that should look like this:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -215,15 +210,15 @@ Vincent Siveton" />
</dependency>
</dependencies>
</project></pre></div>
-<p><tt>pom.xml</tt> contains the Project Object Model (POM) for this project. The POM is the basic unit of work in Maven. This is important to remember because Maven is inherently project-centric in that everything revolves around the notion of a project. In short, the POM contains every important piece of information about your project and is essentially one-stop-shopping for finding anything related to your project. Understanding the POM is important and new users are encouraged to refer to the <a href="../introduction/introduction-to-the-pom.html">Introduction to the POM</a>.</p>
+<p><code>pom.xml</code> contains the Project Object Model (POM) for this project. The POM is the basic unit of work in Maven. This is important to remember because Maven is inherently project-centric in that everything revolves around the notion of a project. In short, the POM contains every important piece of information about your project and is essentially one-stop-shopping for finding anything related to your project. Understanding the POM is important and new users are encouraged to refer to the <a href="../introduction/introduction-to-the-pom.html">Introduction to the POM</a>.</p>
<p>This is a very simple POM but still displays the key elements every POM contains, so let's walk through each of them to familiarize you with the POM essentials:</p>
<ul>
<li><b>project</b> This is the top-level element in all Maven pom.xml files.</li>
<li><b>modelVersion</b> This element indicates what version of the object model this POM is using. The version of the model itself changes very infrequently but it is mandatory in order to ensure stability of use if and when the Maven developers deem it necessary to change the model.</li>
-<li><b>groupId</b> This element indicates the unique identifier of the organization or group that created the project. The groupId is one of the key identifiers of a project and is typically based on the fully qualified domain name of your organization. For example <tt>org.apache.maven.plugins</tt> is the designated groupId for all Maven plugins.</li>
-<li><b>artifactId</b> This element indicates the unique base name of the primary artifact being generated by this project. The primary artifact for a project is typically a JAR file. Secondary artifacts like source bundles also use the artifactId as part of their final name. A typical artifact produced by Maven would have the form <artifactId>-<version>.<extension> (for example, <tt>myapp-1.0.jar</tt>).</li>
-<li><b>packaging</b> This element indicates the package type to be used by this artifact (e.g. JAR, WAR, EAR, etc.). This not only means if the artifact produced is JAR, WAR, or EAR but can also indicate a specific lifecycle to use as part of the build process. (The lifecycle is a topic we will deal with further on in the guide. For now, just keep in mind that the indicated packaging of a project can play a part in customizing the build lifecycle.) The default value for the <tt>packaging</tt> element is JAR so you do not have to specify this for most projects.</li>
-<li><b>version</b> This element indicates the version of the artifact generated by the project. Maven goes a long way to help you with version management and you will often see the <tt>SNAPSHOT</tt> designator in a version, which indicates that a project is in a state of development. We will discuss the use of <a href="./index.html#What_is_a_SNAPSHOT_version">snapshots</a> and how they work further on in this guide.</li>
+<li><b>groupId</b> This element indicates the unique identifier of the organization or group that created the project. The groupId is one of the key identifiers of a project and is typically based on the fully qualified domain name of your organization. For example <code>org.apache.maven.plugins</code> is the designated groupId for all Maven plugins.</li>
+<li><b>artifactId</b> This element indicates the unique base name of the primary artifact being generated by this project. The primary artifact for a project is typically a JAR file. Secondary artifacts like source bundles also use the artifactId as part of their final name. A typical artifact produced by Maven would have the form <artifactId>-<version>.<extension> (for example, <code>myapp-1.0.jar</code>).</li>
+<li><b>packaging</b> This element indicates the package type to be used by this artifact (e.g. JAR, WAR, EAR, etc.). This not only means if the artifact produced is JAR, WAR, or EAR but can also indicate a specific lifecycle to use as part of the build process. (The lifecycle is a topic we will deal with further on in the guide. For now, just keep in mind that the indicated packaging of a project can play a part in customizing the build lifecycle.) The default value for the <code>packaging</code> element is JAR so you do not have to specify this for most projects.</li>
+<li><b>version</b> This element indicates the version of the artifact generated by the project. Maven goes a long way to help you with version management and you will often see the <code>SNAPSHOT</code> designator in a version, which indicates that a project is in a state of development. We will discuss the use of <a href="./index.html#What_is_a_SNAPSHOT_version">snapshots</a> and how they work further on in this guide.</li>
<li><b>name</b> This element indicates the display name used for the project. This is often used in Maven's generated documentation.</li>
<li><b>url</b> This element indicates where the project's site can be found. This is often used in Maven's generated documentation.</li>
<li><b>description</b> This element provides a basic description of your project. This is often used in Maven's generated documentation.</li></ul>
@@ -244,10 +239,9 @@ Vincent Siveton" />
`-- mycompany
`-- app
`-- AppTest.java</pre></div>
-<p>As you can see, the project created from the archetype has a POM, a source tree for your application's sources and a source tree for your test sources. This is the standard layout for Maven projects (the application sources reside in <tt>${basedir}/src/main/java</tt> and test sources reside in <tt>${basedir}/src/test/java</tt>, where ${basedir} represents the directory containing <tt>pom.xml</tt>).</p>
+<p>As you can see, the project created from the archetype has a POM, a source tree for your application's sources and a source tree for your test sources. This is the standard layout for Maven projects (the application sources reside in <code>${basedir}/src/main/java</code> and test sources reside in <code>${basedir}/src/test/java</code>, where ${basedir} represents the directory containing <code>pom.xml</code>).</p>
<p>If you were to create a Maven project by hand this is the directory structure that we recommend using. This is a Maven convention and to learn more about it you can read our <a href="../introduction/introduction-to-the-standard-directory-layout.html">Introduction to the Standard Directory Layout</a>.</p>
-<p>Now that we have a POM, some application sources, and some test sources you are probably asking...</p></div>
-<div class="section">
+<p>Now that we have a POM, some application sources, and some test sources you are probably asking...</p></section><section>
<h3><a name="How_do_I_compile_my_application_sources.3F"></a><a name="How_do_I_compile_my_application_sources">How do I compile my application sources?</a></h3>
<p>Change to the directory where pom.xml is created by archetype:generate and execute the following command to compile your application sources:</p>
<div class="source"><pre class="prettyprint linenums">mvn compile</pre></div>
@@ -274,9 +268,8 @@ Compiling 1 source file to <dir>/m
[INFO] Final Memory: 2M/6M
[INFO] ----------------------------------------------------------------------------</pre></div>
<p>The first time you execute this (or any other) command, Maven will need to download all the plugins and related dependencies it needs to fulfill the command. From a clean installation of Maven, this can take quite a while (in the output above, it took almost 4 minutes). If you execute the command again, Maven will now have what it needs, so it won't need to download anything new and will be able to execute the command much more quickly.</p>
-<p>As you can see from the output, the compiled classes were placed in <tt>${basedir}/target/classes</tt>, which is another standard convention employed by Maven. So, if you're a keen observer, you'll notice that by using the standard conventions, the POM above is very small and you haven't had to tell Maven explicitly where any of your sources are or where the output should go. By following the standard Maven conventions, you can get a lot done with very little effort! Just as a casual comparison, let's take a look at what you might have had to do in <a class="externalLink" href="http://ant.apache.org">Ant</a> to accomplish the same <a href="../../ant/build-a1.xml">thing</a>.</p>
-<p>Now, this is simply to compile a single tree of application sources and the Ant script shown is pretty much the same size as the POM shown above. But we'll see how much more we can do with just that simple POM!</p></div>
-<div class="section">
+<p>As you can see from the output, the compiled classes were placed in <code>${basedir}/target/classes</code>, which is another standard convention employed by Maven. So, if you're a keen observer, you'll notice that by using the standard conventions, the POM above is very small and you haven't had to tell Maven explicitly where any of your sources are or where the output should go. By following the standard Maven conventions, you can get a lot done with very little effort! Just as a casual comparison, let's take a look at what you might have had to do in <a class="externalLink" href="http://ant.apache.org">Ant</a> to accomplish the same <a href="../../ant/build-a1.xml">thing</a>.</p>
+<p>Now, this is simply to compile a single tree of application sources and the Ant script shown is pretty much the same size as the POM shown above. But we'll see how much more we can do with just that simple POM!</p></section><section>
<h3><a name="How_do_I_compile_my_test_sources_and_run_my_unit_tests.3F"></a><a name="How_do_I_compile_my_test_sources_and_run_my_unit_tests">How do I compile my test sources and run my unit tests?</a></h3>
<p>Now you're successfully compiling your application's sources and now you've got some unit tests that you want to compile and execute (because every programmer always writes and executes their unit tests *nudge nudge wink wink*).</p>
<p>Execute the following command:</p>
@@ -321,13 +314,12 @@ Results :
<li>Before compiling and executing the tests Maven compiles the main code (all these classes are up to date because we haven't changed anything since we compiled last).</li></ul>
<p>If you simply want to compile your test sources (but not execute the tests), you can execute the following:</p>
<div class="source"><pre class="prettyprint linenums"> mvn test-compile</pre></div>
-<p>Now that you can compile your application sources, compile your tests, and execute the tests, you'll want to move on to the next logical step so you'll be asking ...</p></div>
-<div class="section">
+<p>Now that you can compile your application sources, compile your tests, and execute the tests, you'll want to move on to the next logical step so you'll be asking ...</p></section><section>
<h3><a name="How_do_I_create_a_JAR_and_install_it_in_my_local_repository.3F"></a><a name="How_do_I_create_a_JAR_and_install_it_in_my_local_repository">How do I create a JAR and install it in my local repository?</a></h3>
<p>Making a JAR file is straight forward enough and can be accomplished by executing the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn package</pre></div>
-<p>If you take a look at the POM for your project you will notice the <tt>packaging</tt> element is set to <tt>jar</tt>. This is how Maven knows to produce a JAR file from the above command (we'll talk more about this later). You can now take a look in the <tt>${basedir}/target</tt> directory and you will see the generated JAR file.</p>
-<p>Now you'll want to install the artifact you've generated (the JAR file) in your local repository (<tt>${user.home}/.m2/repository</tt> is the default location). For more information on repositories you can refer to our <a href="../introduction/introduction-to-repositories.html">Introduction to Repositories</a> but let's move on to installing our artifact! To do so execute the following command:</p>
+<p>If you take a look at the POM for your project you will notice the <code>packaging</code> element is set to <code>jar</code>. This is how Maven knows to produce a JAR file from the above command (we'll talk more about this later). You can now take a look in the <code>${basedir}/target</code> directory and you will see the generated JAR file.</p>
+<p>Now you'll want to install the artifact you've generated (the JAR file) in your local repository (<code>${user.home}/.m2/repository</code> is the default location). For more information on repositories you can refer to our <a href="../introduction/introduction-to-repositories.html">Introduction to Repositories</a> but let's move on to installing our artifact! To do so execute the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn install</pre></div>
<p>Upon executing this command you should see the following output:</p>
<div class="source"><pre class="prettyprint linenums">[INFO] ----------------------------------------------------------------------------
@@ -366,22 +358,21 @@ Results :
[INFO] ----------------------------------------------------------------------------</pre></div>
<p>Note that the surefire plugin (which executes the test) looks for tests contained in files with a particular naming convention. By default the tests included are:</p>
<ul>
-<li><tt>**/*Test.java</tt></li>
-<li><tt>**/Test*.java</tt></li>
-<li><tt>**/*TestCase.java</tt></li></ul>
+<li><code>**/*Test.java</code></li>
+<li><code>**/Test*.java</code></li>
+<li><code>**/*TestCase.java</code></li></ul>
<p>And the default excludes are:</p>
<ul>
-<li><tt>**/Abstract*Test.java</tt></li>
-<li><tt>**/Abstract*TestCase.java</tt></li></ul>
+<li><code>**/Abstract*Test.java</code></li>
+<li><code>**/Abstract*TestCase.java</code></li></ul>
<p>You have walked through the process for setting up, building, testing, packaging, and installing a typical Maven project. This is likely the vast majority of what projects will be doing with Maven and if you've noticed, everything you've been able to do up to this point has been driven by an 18-line file, namely the project's model or POM. If you look at a typical Ant <a href="../../ant/build-a1.xml">build file</a> that provides the same functionality that we've achieved thus far you'll notice it's already twice the size of the POM and we're just getting started! There is far more functionality available to you from Maven without requiring any additions to our POM as it currently stands. To get any more functionality out of our example Ant build file you must keep making error-prone additions.</p>
<p>So what else can you get for free? There are a great number of Maven plugins that work out of the box with even a simple POM like we have above. We'll mention one here specifically as it is one of the highly prized features of Maven: without any work on your part this POM has enough information to generate a web site for your project! You will most likely want to customize your Maven site but if you're pressed for time all you need to do to provide basic information about your project is execute the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
<p>There are plenty of other standalone goals that can be executed as well, for example:</p>
<div class="source"><pre class="prettyprint linenums">mvn clean</pre></div>
-<p>This will remove the <tt>target</tt> directory with all the build data before starting so that it is fresh.</p></div>
-<div class="section">
+<p>This will remove the <code>target</code> directory with all the build data before starting so that it is fresh.</p></section><section>
<h3><a name="What_is_a_SNAPSHOT_version.3F"></a><a name="What_is_a_SNAPSHOT_version">What is a SNAPSHOT version?</a></h3>
-<p>Notice the value of the <b>version</b> tag in the <tt>pom.xml</tt> file shown below has the suffix: <tt>-SNAPSHOT</tt>.</p>
+<p>Notice the value of the <b>version</b> tag in the <code>pom.xml</code> file shown below has the suffix: <code>-SNAPSHOT</code>.</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
...
<groupId>...</groupId>
@@ -390,13 +381,12 @@ Results :
<version>1.0-SNAPSHOT</version>
<name>Maven Quick Start Archetype</name>
...</pre></div>
-<p>The <tt>SNAPSHOT</tt> value refers to the 'latest' code along a development branch, and provides no guarantee the code is stable or unchanging. Conversely, the code in a 'release' version (any version value without the suffix <tt>SNAPSHOT</tt>) is unchanging.</p>
+<p>The <code>SNAPSHOT</code> value refers to the 'latest' code along a development branch, and provides no guarantee the code is stable or unchanging. Conversely, the code in a 'release' version (any version value without the suffix <code>SNAPSHOT</code>) is unchanging.</p>
<p>In other words, a SNAPSHOT version is the 'development' version before the final 'release' version. The SNAPSHOT is "older" than its release.</p>
-<p>During the <a href="../../plugins/maven-release-plugin/">release</a> process, a version of <b>x.y-SNAPSHOT</b> changes to <b>x.y</b>. The release process also increments the development version to <b>x.(y+1)-SNAPSHOT</b>. For example, version <b>1.0-SNAPSHOT</b> is released as version <b>1.0</b>, and the new development version is version <b>1.1-SNAPSHOT</b>.</p></div>
-<div class="section">
+<p>During the <a href="../../plugins/maven-release-plugin/">release</a> process, a version of <b>x.y-SNAPSHOT</b> changes to <b>x.y</b>. The release process also increments the development version to <b>x.(y+1)-SNAPSHOT</b>. For example, version <b>1.0-SNAPSHOT</b> is released as version <b>1.0</b>, and the new development version is version <b>1.1-SNAPSHOT</b>.</p></section><section>
<h3><a name="How_do_I_use_plugins.3F"></a><a name="How_do_I_use_plugins">How do I use plugins?</a></h3>
<p>Whenever you want to customise the build for a Maven project, this is done by adding or reconfiguring plugins.</p>
-<p><b>Note for Maven 1.0 Users:</b> In Maven 1.0, you would have added some <tt>preGoal</tt> to <tt>maven.xml</tt> and some entries to <tt>project.properties</tt>. Here, it is a little different.</p>
+<p><b>Note for Maven 1.0 Users:</b> In Maven 1.0, you would have added some <code>preGoal</code> to <code>maven.xml</code> and some entries to <code>project.properties</code>. Here, it is a little different.</p>
<p>For this example, we will configure the Java compiler to allow JDK 5.0 sources. This is as simple as adding this to your POM:</p>
<div class="source"><pre class="prettyprint linenums">...
<build>
@@ -414,12 +404,11 @@ Results :
</build>
...</pre></div>
<p>You'll notice that all plugins in Maven look much like a dependency - and in some ways they are. This plugin will be automatically downloaded and used - including a specific version if you request it (the default is to use the latest available).</p>
-<p>The <tt>configuration</tt> element applies the given parameters to every goal from the compiler plugin. In the above case, the compiler plugin is already used as part of the build process and this just changes the configuration. It is also possible to add new goals to the process, and configure specific goals. For information on this, see the <a href="../introduction/introduction-to-the-lifecycle.html"> Introduction to the Build Lifecycle</a>.</p>
-<p>To find out what configuration is available for a plugin, you can see the <a href="../../plugins/"> Plugins List</a> and navigate to the plugin and goal you are using. For general information about how to configure the available parameters of a plugin, have a look at the <a href="../mini/guide-configuring-plugins.html">Guide to Configuring Plugins</a>.</p></div>
-<div class="section">
+<p>The <code>configuration</code> element applies the given parameters to every goal from the compiler plugin. In the above case, the compiler plugin is already used as part of the build process and this just changes the configuration. It is also possible to add new goals to the process, and configure specific goals. For information on this, see the <a href="../introduction/introduction-to-the-lifecycle.html"> Introduction to the Build Lifecycle</a>.</p>
+<p>To find out what configuration is available for a plugin, you can see the <a href="../../plugins/"> Plugins List</a> and navigate to the plugin and goal you are using. For general information about how to configure the available parameters of a plugin, have a look at the <a href="../mini/guide-configuring-plugins.html">Guide to Configuring Plugins</a>.</p></section><section>
<h3><a name="How_do_I_add_resources_to_my_JAR.3F"></a><a name="How_do_I_add_resources_to_my_JAR">How do I add resources to my JAR?</a></h3>
<p>Another common use case that can be satisfied which requires no changes to the POM that we have above is packaging resources in the JAR file. For this common task, Maven again relies on the <a href="../introduction/introduction-to-the-standard-directory-layout.html">Standard Directory Layout</a>, which means by using standard Maven conventions you can package resources within JARs simply by placing those resources in a standard directory structure.</p>
-<p>You see below in our example we have added the directory <tt>${basedir}/src/main/resources</tt> into which we place any resources we wish to package in our JAR. The simple rule employed by Maven is this: any directories or files placed within the <tt>${basedir}/src/main/resources</tt> directory are packaged in your JAR with the exact same structure starting at the base of the JAR.</p>
+<p>You see below in our example we have added the directory <code>${basedir}/src/main/resources</code> into which we place any resources we wish to package in our JAR. The simple rule employed by Maven is this: any directories or files placed within the <code>${basedir}/src/main/resources</code> directory are packaged in your JAR with the exact same structure starting at the base of the JAR.</p>
<div class="source"><pre class="prettyprint linenums">my-app
|-- pom.xml
`-- src
@@ -438,7 +427,7 @@ Results :
`-- mycompany
`-- app
`-- AppTest.java</pre></div>
-<p>So you can see in our example that we have a <tt>META-INF</tt> directory with an <tt>application.properties</tt> file within that directory. If you unpacked the JAR that Maven created for you and took a look at it you would see the following:</p>
+<p>So you can see in our example that we have a <code>META-INF</code> directory with an <code>application.properties</code> file within that directory. If you unpacked the JAR that Maven created for you and took a look at it you would see the following:</p>
<div class="source"><pre class="prettyprint linenums">|-- META-INF
| |-- MANIFEST.MF
| |-- application.properties
@@ -451,7 +440,7 @@ Results :
`-- mycompany
`-- app
`-- App.class</pre></div>
-<p>As you can see, the contents of <tt>${basedir}/src/main/resources</tt> can be found starting at the base of the JAR and our <tt>application.properties</tt> file is there in the <tt>META-INF</tt> directory. You will also notice some other files there like <tt>META-INF/MANIFEST.MF</tt> as well as a <tt>pom.xml</tt> and <tt>pom.properties</tt> file. These come standard with generation of a JAR in Maven. You can create your own manifest if you choose, but Maven will generate one by default if you don't. (You can also modify the entries in the default manifest. We will touch on this later.) The <tt>pom.xml</tt> and <tt>pom.properties</tt> files are packaged up in the JAR so that each artifact produced by Maven is self-describing and also allows you to utilize the metadata in your own application if the need arises. One simple use might be to retrieve the version of your application. Operating on the POM file would require you to use some Maven utilities but the properties can be utili
zed using the standard Java API and look like the following:</p>
+<p>As you can see, the contents of <code>${basedir}/src/main/resources</code> can be found starting at the base of the JAR and our <code>application.properties</code> file is there in the <code>META-INF</code> directory. You will also notice some other files there like <code>META-INF/MANIFEST.MF</code> as well as a <code>pom.xml</code> and <code>pom.properties</code> file. These come standard with generation of a JAR in Maven. You can create your own manifest if you choose, but Maven will generate one by default if you don't. (You can also modify the entries in the default manifest. We will touch on this later.) The <code>pom.xml</code> and <code>pom.properties</code> files are packaged up in the JAR so that each artifact produced by Maven is self-describing and also allows you to utilize the metadata in your own application if the need arises. One simple use might be to retrieve the version of your application. Operating on the POM file would require you to use some Maven utilities
but the properties can be utilized using the standard Java API and look like the following:</p>
<div class="source"><pre class="prettyprint linenums">#Generated by Maven
#Tue Oct 04 15:43:21 GMT-05:00 2005
version=1.0-SNAPSHOT
@@ -486,11 +475,10 @@ InputStream is = getClass().getResourceA
// Do something with the resource
-...</pre></div></div>
-<div class="section">
+...</pre></div></section><section>
<h3><a name="How_do_I_filter_resource_files.3F"></a><a name="How_do_I_filter_resource_files">How do I filter resource files?</a></h3>
-<p>Sometimes a resource file will need to contain a value that can only be supplied at build time. To accomplish this in Maven, put a reference to the property that will contain the value into your resource file using the syntax <tt>${<property name>}</tt>. The property can be one of the values defined in your pom.xml, a value defined in the user's settings.xml, a property defined in an external properties file, or a system property.</p>
-<p>To have Maven filter resources when copying, simply set <tt>filtering</tt> to true for the resource directory in your <tt>pom.xml</tt>:</p>
+<p>Sometimes a resource file will need to contain a value that can only be supplied at build time. To accomplish this in Maven, put a reference to the property that will contain the value into your resource file using the syntax <code>${<property name>}</code>. The property can be one of the values defined in your pom.xml, a value defined in the user's settings.xml, a property defined in an external properties file, or a system property.</p>
+<p>To have Maven filter resources when copying, simply set <code>filtering</code> to true for the resource directory in your <code>pom.xml</code>:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -523,22 +511,22 @@ InputStream is = getClass().getResourceA
</resources>
</build>
</project></pre></div>
-<p>You'll notice that we had to add the <tt>build</tt>, <tt>resources</tt>, and <tt>resource</tt> elements which weren't there before. In addition, we had to explicitly state that the resources are located in the src/main/resources directory. All of this information was provided as default values previously, but because the default value for <tt>filtering</tt> is false, we had to add this to our pom.xml in order to override that default value and set <tt>filtering</tt> to true.</p>
-<p>To reference a property defined in your pom.xml, the property name uses the names of the XML elements that define the value, with "pom" being allowed as an alias for the project (root) element. So <tt>${project.name}</tt> refers to the name of the project, <tt>${project.version}</tt> refers to the version of the project, <tt>${project.build.finalName}</tt> refers to the final name of the file created when the built project is packaged, etc. Note that some elements of the POM have default values, so don't need to be explicitly defined in your <tt>pom.xml</tt> for the values to be available here. Similarly, values in the user's <tt>settings.xml</tt> can be referenced using property names beginning with "settings" (for example, <tt>${settings.localRepository}</tt> refers to the path of the user's local repository).</p>
-<p>To continue our example, let's add a couple of properties to the <tt>application.properties</tt> file (which we put in the <tt>src/main/resources</tt> directory) whose values will be supplied when the resource is filtered:</p>
+<p>You'll notice that we had to add the <code>build</code>, <code>resources</code>, and <code>resource</code> elements which weren't there before. In addition, we had to explicitly state that the resources are located in the src/main/resources directory. All of this information was provided as default values previously, but because the default value for <code>filtering</code> is false, we had to add this to our pom.xml in order to override that default value and set <code>filtering</code> to true.</p>
+<p>To reference a property defined in your pom.xml, the property name uses the names of the XML elements that define the value, with "pom" being allowed as an alias for the project (root) element. So <code>${project.name}</code> refers to the name of the project, <code>${project.version}</code> refers to the version of the project, <code>${project.build.finalName}</code> refers to the final name of the file created when the built project is packaged, etc. Note that some elements of the POM have default values, so don't need to be explicitly defined in your <code>pom.xml</code> for the values to be available here. Similarly, values in the user's <code>settings.xml</code> can be referenced using property names beginning with "settings" (for example, <code>${settings.localRepository}</code> refers to the path of the user's local repository).</p>
+<p>To continue our example, let's add a couple of properties to the <code>application.properties</code> file (which we put in the <code>src/main/resources</code> directory) whose values will be supplied when the resource is filtered:</p>
<div class="source"><pre class="prettyprint linenums"># application.properties
application.name=${project.name}
application.version=${project.version}</pre></div>
<p>With that in place, you can execute the following command (process-resources is the build lifecycle phase where the resources are copied and filtered):</p>
<div class="source"><pre class="prettyprint linenums">mvn process-resources</pre></div>
-<p>and the <tt>application.properties</tt> file under <tt>target/classes</tt> (and will eventually go into the jar) looks like this:</p>
+<p>and the <code>application.properties</code> file under <code>target/classes</code> (and will eventually go into the jar) looks like this:</p>
<div class="source"><pre class="prettyprint linenums"># application.properties
application.name=Maven Quick Start Archetype
application.version=1.0-SNAPSHOT</pre></div>
-<p>To reference a property defined in an external file, all you need to do is add a reference to this external file in your pom.xml. First, let's create our external properties file and call it <tt>src/main/filters/filter.properties</tt>:</p>
+<p>To reference a property defined in an external file, all you need to do is add a reference to this external file in your pom.xml. First, let's create our external properties file and call it <code>src/main/filters/filter.properties</code>:</p>
<div class="source"><pre class="prettyprint linenums"># filter.properties
my.filter.value=hello!</pre></div>
-<p>Next, we'll add a reference to this new file in the <tt>pom.xml</tt>:</p>
+<p>Next, we'll add a reference to this new file in the <code>pom.xml</code>:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -574,12 +562,12 @@ my.filter.value=hello!</pre></div>
</resources>
</build>
</project></pre></div>
-<p>Then, if we add a reference to this property in the <tt>application.properties</tt> file:</p>
+<p>Then, if we add a reference to this property in the <code>application.properties</code> file:</p>
<div class="source"><pre class="prettyprint linenums"># application.properties
application.name=${project.name}
application.version=${project.version}
message=${my.filter.value}</pre></div>
-<p>the next execution of the <tt>mvn process-resources</tt> command will put our new property value into <tt>application.properties</tt>. As an alternative to defining the my.filter.value property in an external file, you could also have defined it in the <tt>properties</tt> section of your <tt>pom.xml</tt> and you'd get the same effect (notice I don't need the references to <tt>src/main/filters/filter.properties</tt> either):</p>
+<p>the next execution of the <code>mvn process-resources</code> command will put our new property value into <code>application.properties</code>. As an alternative to defining the my.filter.value property in an external file, you could also have defined it in the <code>properties</code> section of your <code>pom.xml</code> and you'd get the same effect (notice I don't need the references to <code>src/main/filters/filter.properties</code> either):</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -616,16 +604,15 @@ message=${my.filter.value}</pre></div>
<my.filter.value>hello</my.filter.value>
</properties>
</project></pre></div>
-<p>Filtering resources can also get values from system properties; either the system properties built into Java (like <tt>java.version</tt> or <tt>user.home</tt>) or properties defined on the command line using the standard Java -D parameter. To continue the example, let's change our <tt>application.properties</tt> file to look like this:</p>
+<p>Filtering resources can also get values from system properties; either the system properties built into Java (like <code>java.version</code> or <code>user.home</code>) or properties defined on the command line using the standard Java -D parameter. To continue the example, let's change our <code>application.properties</code> file to look like this:</p>
<div class="source"><pre class="prettyprint linenums"># application.properties
java.version=${java.version}
command.line.prop=${command.line.prop}</pre></div>
-<p>Now, when you execute the following command (note the definition of the command.line.prop property on the command line), the <tt>application.properties</tt> file will contain the values from the system properties.</p>
-<div class="source"><pre class="prettyprint linenums">mvn process-resources "-Dcommand.line.prop=hello again"</pre></div></div>
-<div class="section">
+<p>Now, when you execute the following command (note the definition of the command.line.prop property on the command line), the <code>application.properties</code> file will contain the values from the system properties.</p>
+<div class="source"><pre class="prettyprint linenums">mvn process-resources "-Dcommand.line.prop=hello again"</pre></div></section><section>
<h3><a name="How_do_I_use_external_dependencies.3F"></a><a name="How_do_I_use_external_dependencies">How do I use external dependencies?</a></h3>
-<p>You've probably already noticed a <tt>dependencies</tt> element in the POM we've been using as an example. You have, in fact, been using an external dependency all this time, but here we'll talk about how this works in a bit more detail. For a more thorough introduction, please refer to our <a href="../introduction/introduction-to-dependency-mechanism.html">Introduction to Dependency Mechanism</a>.</p>
-<p>The <tt>dependencies</tt> section of the pom.xml lists all of the external dependencies that our project needs in order to build (whether it needs that dependency at compile time, test time, run time, or whatever). Right now, our project is depending on JUnit only (I took out all of the resource filtering stuff for clarity):</p>
+<p>You've probably already noticed a <code>dependencies</code> element in the POM we've been using as an example. You have, in fact, been using an external dependency all this time, but here we'll talk about how this works in a bit more detail. For a more thorough introduction, please refer to our <a href="../introduction/introduction-to-dependency-mechanism.html">Introduction to Dependency Mechanism</a>.</p>
+<p>The <code>dependencies</code> section of the pom.xml lists all of the external dependencies that our project needs in order to build (whether it needs that dependency at compile time, test time, run time, or whatever). Right now, our project is depending on JUnit only (I took out all of the resource filtering stuff for clarity):</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -649,9 +636,9 @@ command.line.prop=${command.line.prop}</
</dependency>
</dependencies>
</project></pre></div>
-<p>For each external dependency, you'll need to define at least 4 things: groupId, artifactId, version, and scope. The groupId, artifactId, and version are the same as those given in the <tt>pom.xml</tt> for the project that built that dependency. The scope element indicates how your project uses that dependency, and can be values like <tt>compile</tt>, <tt>test</tt>, and <tt>runtime</tt>. For more information on everything you can specify for a dependency, see the <a href="/ref/current/maven-model/maven.html">Project Descriptor Reference</a>.</p>
+<p>For each external dependency, you'll need to define at least 4 things: groupId, artifactId, version, and scope. The groupId, artifactId, and version are the same as those given in the <code>pom.xml</code> for the project that built that dependency. The scope element indicates how your project uses that dependency, and can be values like <code>compile</code>, <code>test</code>, and <code>runtime</code>. For more information on everything you can specify for a dependency, see the <a href="/ref/current/maven-model/maven.html">Project Descriptor Reference</a>.</p>
<p>For more information about the dependency mechanism as a whole, see <a href="../introduction/introduction-to-dependency-mechanism.html">Introduction to Dependency Mechanism</a>.</p>
-<p>With this information about a dependency, Maven will be able to reference the dependency when it builds the project. Where does Maven reference the dependency from? Maven looks in your local repository (<tt>${user.home}/.m2/repository</tt> is the default location) to find all dependencies. In a <a href="#How_do_I_create_a_JAR_and_install_it_in_my_local_repository">previous section</a>, we installed the artifact from our project (my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed there, another project can reference that jar as a dependency simply by adding the dependency information to its pom.xml:</p>
+<p>With this information about a dependency, Maven will be able to reference the dependency when it builds the project. Where does Maven reference the dependency from? Maven looks in your local repository (<code>${user.home}/.m2/repository</code> is the default location) to find all dependencies. In a <a href="#How_do_I_create_a_JAR_and_install_it_in_my_local_repository">previous section</a>, we installed the artifact from our project (my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed there, another project can reference that jar as a dependency simply by adding the dependency information to its pom.xml:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -720,8 +707,7 @@ command.line.prop=${command.line.prop}</
</dependency>
</dependencies>
</project></pre></div>
-<p>Now, when we compile the project (<tt>mvn compile</tt>), we'll see Maven download the log4j dependency for us.</p></div>
-<div class="section">
+<p>Now, when we compile the project (<code>mvn compile</code>), we'll see Maven download the log4j dependency for us.</p></section><section>
<h3><a name="How_do_I_deploy_my_jar_in_my_remote_repository.3F"></a><a name="How_do_I_deploy_my_jar_in_my_remote_repository">How do I deploy my jar in my remote repository?</a></h3>
<p>For deploying jars to an external repository, you have to configure the repository url in the pom.xml and the authentication information for connectiong to the repository in the settings.xml.</p>
<p>Here is an example using scp and username/password authentication:</p>
@@ -794,8 +780,7 @@ command.line.prop=${command.line.prop}</
...
</settings></pre></div>
<p>Note that if you are connecting to an openssh ssh server which has the parameter "PasswordAuthentication" set to "no" in the sshd_confing, you will have to type your password each time for username/password authentication (although you can log in using another ssh client by typing in the username and password). You might want to switch to public key authentication in this case.</p>
-<p>Care should be taken if using passwords in <tt>settings.xml</tt>. For more information, see <a href="../mini/guide-encryption.html"> Password Encryption</a>.</p></div>
-<div class="section">
+<p>Care should be taken if using passwords in <code>settings.xml</code>. For more information, see <a href="../mini/guide-encryption.html"> Password Encryption</a>.</p></section><section>
<h3><a name="How_do_I_create_documentation.3F"></a><a name="How_do_I_create_documentation">How do I create documentation?</a></h3>
<p>To get you jump started with Maven's documentation system you can use the archetype mechanism to generate a site for your existing project using the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn archetype:generate \
@@ -803,8 +788,7 @@ command.line.prop=${command.line.prop}</
-DarchetypeArtifactId=maven-archetype-site \
-DgroupId=com.mycompany.app \
-DartifactId=my-app-site</pre></div>
-<p>Now head on over to the <a href="../mini/guide-site.html">Guide to creating a site</a> to learn how to create the documentation for your project.</p></div>
-<div class="section">
+<p>Now head on over to the <a href="../mini/guide-site.html">Guide to creating a site</a> to learn how to create the documentation for your project.</p></section><section>
<h3><a name="How_do_I_build_other_types_of_projects.3F"></a><a name="How_do_I_build_other_types_of_projects">How do I build other types of projects?</a></h3>
<p>Note that the lifecycle applies to any project type. For example, back in the base directory we can create a simple web application:</p>
<div class="source"><pre class="prettyprint linenums">mvn archetype:generate \
@@ -812,7 +796,7 @@ command.line.prop=${command.line.prop}</
-DarchetypeArtifactId=maven-archetype-webapp \
-DgroupId=com.mycompany.app \
-DartifactId=my-webapp</pre></div>
-<p>Note that these must all be on a single line. This will create a directory called <tt>my-webapp</tt> containing the following project descriptor:</p>
+<p>Note that these must all be on a single line. This will create a directory called <code>my-webapp</code> containing the following project descriptor:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -837,13 +821,12 @@ command.line.prop=${command.line.prop}</
<finalName>my-webapp</finalName>
</build>
</project></pre></div>
-<p>Note the <tt><packaging></tt> element - this tells Maven to build as a WAR. Change into the webapp project's directory and try:</p>
+<p>Note the <code><packaging></code> element - this tells Maven to build as a WAR. Change into the webapp project's directory and try:</p>
<div class="source"><pre class="prettyprint linenums">mvn package</pre></div>
-<p>You'll see <tt>target/my-webapp.war</tt> is built, and that all the normal steps were executed.</p></div>
-<div class="section">
+<p>You'll see <code>target/my-webapp.war</code> is built, and that all the normal steps were executed.</p></section><section>
<h3><a name="How_do_I_build_more_than_one_project_at_once.3F"></a><a name="How_do_I_build_more_than_one_project_at_once">How do I build more than one project at once?</a></h3>
<p>The concept of dealing with multiple modules is built in to Maven. In this section, we will show how to build the WAR above, and include the previous JAR as well in one step.</p>
-<p>Firstly, we need to add a parent <tt>pom.xml</tt> file in the directory above the other two, so it should look like this:</p>
+<p>Firstly, we need to add a parent <code>pom.xml</code> file in the directory above the other two, so it should look like this:</p>
<div class="source"><pre class="prettyprint linenums">+- pom.xml
+- my-app
| +- pom.xml
@@ -872,7 +855,7 @@ command.line.prop=${command.line.prop}</
<module>my-webapp</module>
</modules>
</project></pre></div>
-<p>We'll need a dependency on the JAR from the webapp, so add this to <tt>my-webapp/pom.xml</tt>:</p>
+<p>We'll need a dependency on the JAR from the webapp, so add this to <code>my-webapp/pom.xml</code>:</p>
<div class="source"><pre class="prettyprint linenums"> ...
<dependencies>
<dependency>
@@ -882,7 +865,7 @@ command.line.prop=${command.line.prop}</
</dependency>
...
</dependencies></pre></div>
-<p>Finally, add the following <tt><parent></tt> element to both of the other <tt>pom.xml</tt> files in the subdirectories:</p>
+<p>Finally, add the following <code><parent></code> element to both of the other <code>pom.xml</code> files in the subdirectories:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@@ -895,7 +878,7 @@ command.line.prop=${command.line.prop}</
...</pre></div>
<p>Now, try it... from the top level directory, run:</p>
<div class="source"><pre class="prettyprint linenums">mvn verify</pre></div>
-<p>The WAR has now been created in <tt>my-webapp/target/my-webapp.war</tt>, and the JAR is included:</p>
+<p>The WAR has now been created in <code>my-webapp/target/my-webapp.war</code>, and the JAR is included:</p>
<div class="source"><pre class="prettyprint linenums">$ jar tvf my-webapp/target/my-webapp-1.0-SNAPSHOT.war
0 Fri Jun 24 10:59:56 EST 2005 META-INF/
222 Fri Jun 24 10:59:54 EST 2005 META-INF/MANIFEST.MF
@@ -909,10 +892,10 @@ command.line.prop=${command.line.prop}</
52 Fri Jun 24 10:59:56 EST 2005 index.jsp
0 Fri Jun 24 10:59:56 EST 2005 WEB-INF/lib/
2713 Fri Jun 24 10:59:56 EST 2005 WEB-INF/lib/my-app-1.0-SNAPSHOT.jar</pre></div>
-<p>How does this work? Firstly, the parent POM created (called <tt>app</tt>), has a packaging of <tt>pom</tt> and a list of modules defined. This tells Maven to run all operations over the set of projects instead of just the current one (to override this behaviour, you can use the <tt>--non-recursive</tt> command line option).</p>
-<p>Next, we tell the WAR that it requires the <tt>my-app</tt> JAR. This does a few things: it makes it available on the classpath to any code in the WAR (none in this case), it makes sure the JAR is always built before the WAR, and it indicates to the WAR plugin to include the JAR in its library directory.</p>
-<p>You may have noticed that <tt>junit-4.11.jar</tt> was a dependency, but didn't end up in the WAR. The reason for this is the <tt><scope>test</scope></tt> element - it is only required for testing, and so is not included in the web application as the compile time dependency <tt>my-app</tt> is.</p>
-<p>The final step was to include a parent definition. This is different to the <tt>extend</tt> element you may be familiar with from Maven 1.0: this ensures that the POM can always be located even if the project is distributed separately from its parent by looking it up in the repository.</p></div></div>
+<p>How does this work? Firstly, the parent POM created (called <code>app</code>), has a packaging of <code>pom</code> and a list of modules defined. This tells Maven to run all operations over the set of projects instead of just the current one (to override this behaviour, you can use the <code>--non-recursive</code> command line option).</p>
+<p>Next, we tell the WAR that it requires the <code>my-app</code> JAR. This does a few things: it makes it available on the classpath to any code in the WAR (none in this case), it makes sure the JAR is always built before the WAR, and it indicates to the WAR plugin to include the JAR in its library directory.</p>
+<p>You may have noticed that <code>junit-4.11.jar</code> was a dependency, but didn't end up in the WAR. The reason for this is the <code><scope>test</scope></code> element - it is only required for testing, and so is not included in the web application as the compile time dependency <code>my-app</code> is.</p>
+<p>The final step was to include a parent definition. This is different to the <code>extend</code> element you may be familiar with from Maven 1.0: this ensures that the POM can always be located even if the project is distributed separately from its parent by looking it up in the repository.</p></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/getting-started/maven-in-five-minutes.html
==============================================================================
--- maven/website/content/guides/getting-started/maven-in-five-minutes.html (original)
+++ maven/website/content/guides/getting-started/maven-in-five-minutes.html 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/getting-started/maven-in-five-minutes.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/getting-started/maven-in-five-minutes.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">
@@ -135,12 +135,10 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Maven_in_5_Minutes"></a>Maven in 5 Minutes</h2>
-<div class="section">
+<section>
+<h2><a name="Maven_in_5_Minutes"></a>Maven in 5 Minutes</h2><section>
<h3><a name="Prerequisites"></a>Prerequisites</h3>
-<p>You must have an understanding of how to install software on your computer. If you do not know how to do this, please ask someone at your office, school, etc or pay someone to explain this to you. The Maven mailing lists are not the best place to ask for this advice.</p></div>
-<div class="section">
+<p>You must have an understanding of how to install software on your computer. If you do not know how to do this, please ask someone at your office, school, etc or pay someone to explain this to you. The Maven mailing lists are not the best place to ask for this advice.</p></section><section>
<h3><a name="Installation"></a>Installation</h3>
<p><i>Maven is a Java tool, so you must have <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java</a> installed in order to proceed.</i></p>
<p>First, <a href="../../download.html">download Maven</a> and follow the <a href="../../install.html">installation instructions</a>. After that, type the following in a terminal or in a command prompt:</p>
@@ -152,8 +150,7 @@ Java version: 1.8.0_161, vendor: Oracle
Default locale: nl_NL, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"</pre></div>
<p>Depending upon your network setup, you may require extra configuration. Check out the <a href="../mini/guide-configuring-maven.html">Guide to Configuring Maven</a> if necessary.</p>
-<p><b>If you are using Windows, you should look at</b> <a href="./windows-prerequisites.html">Windows Prerequisites</a> <b>to ensure that you are prepared to use Maven on Windows.</b></p></div>
-<div class="section">
+<p><b>If you are using Windows, you should look at</b> <a href="./windows-prerequisites.html">Windows Prerequisites</a> <b>to ensure that you are prepared to use Maven on Windows.</b></p></section><section>
<h3><a name="Creating_a_Project"></a>Creating a Project</h3>
<p>You will need somewhere for your project to reside, create a directory somewhere and start a shell in that directory. On your command line, execute the following Maven goal:</p>
<div class="source"><pre class="prettyprint linenums">mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DinteractiveMode=false</pre></div>
@@ -176,10 +173,9 @@ OS name: "windows 7", version:
`-- mycompany
`-- app
`-- AppTest.java</pre></div>
-<p>The <tt>src/main/java</tt> directory contains the project source code, the <tt>src/test/java</tt> directory contains the test source, and the <tt>pom.xml</tt> file is the project's Project Object Model, or POM.</p>
-<div class="section">
+<p>The <code>src/main/java</code> directory contains the project source code, the <code>src/test/java</code> directory contains the test source, and the <code>pom.xml</code> file is the project's Project Object Model, or POM.</p><section>
<h4><a name="The_POM"></a>The POM</h4>
-<p>The <tt>pom.xml</tt> file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:</p>
+<p>The <code>pom.xml</code> file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -201,11 +197,9 @@ OS name: "windows 7", version:
<scope>test</scope>
</dependency>
</dependencies>
-</project></pre></div></div>
-<div class="section">
+</project></pre></div></section><section>
<h4><a name="What_did_I_just_do.3F"></a>What did I just do?</h4>
-<p>You executed the Maven goal <i>archetype:generate</i>, and passed in various parameters to that goal. The prefix <i>archetype</i> is the <a href="../../plugins/index.html">plugin</a> that provides the goal. If you are familiar with <a class="externalLink" href="http://ant.apache.org">Ant</a>, you may conceive of this as similar to a task. This <i>archetype:generate</i> goal created a simple project based upon a <a href="/archetypes/maven-archetype-quickstart/">maven-archetype-quickstart</a> archetype. Suffice it to say for now that a <i>plugin</i> is a collection of <i>goals</i> with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".</p></div>
-<div class="section">
+<p>You executed the Maven goal <i>archetype:generate</i>, and passed in various parameters to that goal. The prefix <i>archetype</i> is the <a href="../../plugins/index.html">plugin</a> that provides the goal. If you are familiar with <a class="externalLink" href="http://ant.apache.org">Ant</a>, you may conceive of this as similar to a task. This <i>archetype:generate</i> goal created a simple project based upon a <a href="/archetypes/maven-archetype-quickstart/">maven-archetype-quickstart</a> archetype. Suffice it to say for now that a <i>plugin</i> is a collection of <i>goals</i> with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".</p></section><section>
<h4><a name="Build_the_Project"></a>Build the Project</h4>
<div class="source"><pre class="prettyprint linenums">mvn package</pre></div>
<p>The command line will print out various actions, and end with the following:</p>
@@ -228,11 +222,10 @@ OS name: "windows 7", version:
<p>You may test the newly compiled and packaged JAR with the following command:</p>
<div class="source"><pre class="prettyprint linenums">java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App</pre></div>
<p>Which will print the quintessential:</p>
-<div class="source"><pre class="prettyprint linenums">Hello World!</pre></div></div></div>
-<div class="section">
+<div class="source"><pre class="prettyprint linenums">Hello World!</pre></div></section></section><section>
<h3><a name="Java_9_or_later"></a>Java 9 or later</h3>
-<p>By default your version of Maven might use an old version of the <tt>maven-compiler-plugin</tt> that is not compatible with Java 9 or later versions. To target Java 9 or later, you should at least use version 3.6.0 of the <tt>maven-compiler-plugin</tt> and set the <tt>maven.compiler.release</tt> property to the Java release you are targetting (e.g. 9, 10, 11, 12, etc.).</p>
-<p>In the following example, we have configured our Maven project to use version 3.8.1 of <tt>maven-compiler-plugin</tt> and target Java 11:</p>
+<p>By default your version of Maven might use an old version of the <code>maven-compiler-plugin</code> that is not compatible with Java 9 or later versions. To target Java 9 or later, you should at least use version 3.6.0 of the <code>maven-compiler-plugin</code> and set the <code>maven.compiler.release</code> property to the Java release you are targetting (e.g. 9, 10, 11, 12, etc.).</p>
+<p>In the following example, we have configured our Maven project to use version 3.8.1 of <code>maven-compiler-plugin</code> and target Java 11:</p>
<div class="source"><pre class="prettyprint linenums"> <properties>
<maven.compiler.release>11</maven.compiler.release>
</properties>
@@ -248,10 +241,8 @@ OS name: "windows 7", version:
</plugins>
</pluginManagement>
</build></pre></div>
-<p>To learn more about <tt>javac</tt>'s <tt>--release</tt> option, see <a class="externalLink" href="https://openjdk.java.net/jeps/247">JEP 247</a>.</p></div>
-<div class="section">
-<h3><a name="Running_Maven_Tools"></a>Running Maven Tools</h3>
-<div class="section">
+<p>To learn more about <code>javac</code>'s <code>--release</code> option, see <a class="externalLink" href="https://openjdk.java.net/jeps/247">JEP 247</a>.</p></section><section>
+<h3><a name="Running_Maven_Tools"></a>Running Maven Tools</h3><section>
<h4><a name="Maven_Phases"></a>Maven Phases</h4>
<p>Although hardly a comprehensive list, these are the most common <i>default</i> lifecycle phases executed.</p>
<ul>
@@ -271,14 +262,12 @@ OS name: "windows 7", version:
<p>Phases are actually mapped to underlying goals. The specific goals executed per phase is dependant upon the packaging type of the project. For example, <i>package</i> executes <i>jar:jar</i> if the project type is a JAR, and <i>war:war</i> if the project type is - you guessed it - a WAR.</p>
<p>An interesting thing to note is that phases and goals may be executed in sequence.</p>
<div class="source"><pre class="prettyprint linenums">mvn clean dependency:copy-dependencies package</pre></div>
-<p>This command will clean the project, copy dependencies, and package the project (executing all phases up to <i>package</i>, of course).</p></div>
-<div class="section">
+<p>This command will clean the project, copy dependencies, and package the project (executing all phases up to <i>package</i>, of course).</p></section><section>
<h4><a name="Generating_the_Site"></a>Generating the Site</h4>
<div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
-<p>This phase generates a site based upon information on the project's pom. You can look at the documentation generated under <tt>target/site</tt>.</p></div></div>
-<div class="section">
+<p>This phase generates a site based upon information on the project's pom. You can look at the documentation generated under <code>target/site</code>.</p></section></section><section>
<h3><a name="Conclusion"></a>Conclusion</h3>
-<p>We hope this quick overview has piqued your interest in the versatility of Maven. Note that this is a very truncated quick-start guide. Now you are ready for more comprehensive details concerning the actions you have just performed. Check out the <a href="./index.html">Maven Getting Started Guide</a>.</p></div></div>
+<p>We hope this quick overview has piqued your interest in the versatility of Maven. Note that this is a very truncated quick-start guide. Now you are ready for more comprehensive details concerning the actions you have just performed. Check out the <a href="./index.html">Maven Getting Started Guide</a>.</p></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/getting-started/windows-prerequisites.html
==============================================================================
--- maven/website/content/guides/getting-started/windows-prerequisites.html (original)
+++ maven/website/content/guides/getting-started/windows-prerequisites.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/getting-started/windows-prerequisites.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/getting-started/windows-prerequisites.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,27 +120,22 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Maven_on_Windows"></a>Maven on Windows</h2>
-<p>Maven is a command-line tool for building Java (and other) programs. The Maven project provides a simple ZIP file containing a precompiled version of Maven for your convenience. There is no installer. It's up to you to set up your prerequisites and environment to run Maven on Windows.</p>
-<div class="section">
+<p>Maven is a command-line tool for building Java (and other) programs. The Maven project provides a simple ZIP file containing a precompiled version of Maven for your convenience. There is no installer. It's up to you to set up your prerequisites and environment to run Maven on Windows.</p><section>
<h3><a name="Spaces_in_Pathnames"></a>Spaces in Pathnames</h3>
-<p>Maven, like many cross-platform tools, can encounter problems when there are space characters in important pathnames. The instructions below will remind you of this for several particular items.</p></div>
-<div class="section">
+<p>Maven, like many cross-platform tools, can encounter problems when there are space characters in important pathnames. The instructions below will remind you of this for several particular items.</p></section><section>
<h3><a name="Prerequisites"></a>Prerequisites</h3>
-<p>Maven is written in Java (and primarily used to build Java programs). Thus, the major prerequisite is the Java SDK. You need to install the Java SDK (e.g. from <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Oracle's download site</a>), and you should install it to a pathname without spaces, such as <tt>c:\j2se1.6</tt>.</p>
+<p>Maven is written in Java (and primarily used to build Java programs). Thus, the major prerequisite is the Java SDK. You need to install the Java SDK (e.g. from <a class="externalLink" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Oracle's download site</a>), and you should install it to a pathname without spaces, such as <code>c:\j2se1.6</code>.</p>
<p>Once Java is installed, you must ensure that the commands from the Java SDK are in your PATH environment variable. Running, for example,</p>
<div class="source"><pre class="prettyprint linenums">java -version</pre></div>
-<p>must show the right version number.</p></div>
-<div class="section">
+<p>must show the right version number.</p></section><section>
<h3><a name="Maven_Unpacked"></a>Maven Unpacked</h3>
-<p>You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location (with no spaces in the path!) and unpack it there. Let's assume that the path is <tt>${maven.home}</tt>.</p></div>
-<div class="section">
+<p>You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location (with no spaces in the path!) and unpack it there. Let's assume that the path is <code>${maven.home}</code>.</p></section><section>
<h3><a name="Maven_in_PATH"></a>Maven in PATH</h3>
-<p>You run Maven by invoking a command-line tool: <tt>mvn.cmd</tt> from the <tt>bin</tt> directory of the Maven. To do this conveniently, <tt>${maven.home}\bin</tt> must be in your PATH, just like the Java SDK commands. You can add directories to your <tt>PATH</tt> in the control panel; the details vary by Windows version.</p></div>
-<div class="section">
+<p>You run Maven by invoking a command-line tool: <code>mvn.cmd</code> from the <code>bin</code> directory of the Maven. To do this conveniently, <code>${maven.home}\bin</code> must be in your PATH, just like the Java SDK commands. You can add directories to your <code>PATH</code> in the control panel; the details vary by Windows version.</p></section><section>
<h3><a name="Firewalls_and_Anti-virus"></a>Firewalls and Anti-virus</h3>
-<p>Firewall and Anti-virus sometimes prevent Java from running properly, or Windows Firewall (and various other Firewalls) actively prevent Java.exe from reaching out to the Internet to "download stuff" which is a key part of Maven. You may need to configure the Firewall or Anti-virus to add exceptions to allow such actions.</p></div></div>
+<p>Firewall and Anti-virus sometimes prevent Java from running properly, or Windows Firewall (and various other Firewalls) actively prevent Java.exe from reaching out to the Internet to "download stuff" which is a key part of Maven. You may need to configure the Firewall or Anti-virus to add exceptions to allow such actions.</p></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/index.html
==============================================================================
--- maven/website/content/guides/index.html (original)
+++ maven/website/content/guides/index.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/index.apt.vm at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/index.apt.vm 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">
@@ -121,14 +121,12 @@ Eric Redmond" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Documentation"></a>Documentation</h2>
-<div class="section">
+<section>
+<h2><a name="Documentation"></a>Documentation</h2><section>
<h3><a name="Getting_Started_with_Maven"></a>Getting Started with Maven</h3>
<ul>
<li><a href="./getting-started/maven-in-five-minutes.html">Getting Started in 5 Minutes</a></li>
-<li><a href="./getting-started/index.html">Getting Started in 30 Minutes</a></li></ul></div>
-<div class="section">
+<li><a href="./getting-started/index.html">Getting Started in 30 Minutes</a></li></ul></section><section>
<h3><a name="Introductions"></a>Introductions</h3>
<ul>
<li><a href="./introduction/introduction-to-the-lifecycle.html">The Build Lifecycle</a></li>
@@ -138,37 +136,31 @@ Eric Redmond" />
<li><a href="./introduction/introduction-to-the-standard-directory-layout.html">Standard Directory Layout</a></li>
<li><a href="./introduction/introduction-to-dependency-mechanism.html">The Dependency Mechanism</a>
<ul>
-<li><a href="./introduction/introduction-to-optional-and-excludes-dependencies.html"> Optional Dependencies and Dependency Exclusions</a></li></ul></li></ul>
-<div class="section">
+<li><a href="./introduction/introduction-to-optional-and-excludes-dependencies.html"> Optional Dependencies and Dependency Exclusions</a></li></ul></li></ul><section>
<h4><a name="Plugins"></a>Plugins</h4>
<ul>
<li><a href="./introduction/introduction-to-plugins.html">Plugin Development</a></li>
<li><a href="./mini/guide-configuring-plugins.html">Configuring Plug-ins</a></li>
<li><a href="./introduction/introduction-to-plugin-prefix-mapping.html">Plugin Prefix Resolution</a></li>
-<li><a href="./plugin/guide-java-plugin-development.html">Developing Java Plugins</a></li></ul></div>
-<div class="section">
+<li><a href="./plugin/guide-java-plugin-development.html">Developing Java Plugins</a></li></ul></section><section>
<h4><a name="Site"></a>Site</h4>
<ul>
<li><a href="./mini/guide-site.html">Creating a Site</a></li>
<li><a href="/doxia/references/apt-format.html">The APT Format</a></li>
-<li><a href="./mini/guide-snippet-macro.html">Snippet Macro</a></li></ul></div>
-<div class="section">
+<li><a href="./mini/guide-snippet-macro.html">Snippet Macro</a></li></ul></section><section>
<h4><a name="Archetypes"></a>Archetypes</h4>
<ul>
<li><a href="./introduction/introduction-to-archetypes.html">What is an Archetype</a></li>
-<li><a href="./mini/guide-creating-archetypes.html">Creating Archetypes</a></li></ul></div>
-<div class="section">
+<li><a href="./mini/guide-creating-archetypes.html">Creating Archetypes</a></li></ul></section><section>
<h4><a name="Upgrading"></a>Upgrading</h4>
<ul>
-<li><a href="./mini/guide-relocation.html">Relocation of Artifacts</a></li></ul></div>
-<div class="section">
+<li><a href="./mini/guide-relocation.html">Relocation of Artifacts</a></li></ul></section><section>
<h4><a name="Repositories"></a>Repositories</h4>
<ul>
<li><a href="./mini/guide-3rd-party-jars-local.html">Installing 3rd party JARs to Local Repository</a></li>
<li><a href="./mini/guide-3rd-party-jars-remote.html">Deploying 3rd party JARs to Remote Repository</a></li>
<li><a href="./mini/guide-coping-with-sun-jars.html">Coping with Sun JARs</a></li>
-<li><a href="./mini/guide-repository-ssl.html">Remote repository access through authenticated HTTPS</a></li></ul></div></div>
-<div class="section">
+<li><a href="./mini/guide-repository-ssl.html">Remote repository access through authenticated HTTPS</a></li></ul></section></section><section>
<h3><a name="Guides"></a>Guides</h3>
<ul>
<li><a href="./mini/guide-assemblies.html">Creating Assemblies</a></li>
@@ -192,39 +184,33 @@ Eric Redmond" />
<li><a href="./mini/guide-http-settings.html"> Guide to HTTP Connection Settings</a></li>
<li><a href="./mini/guide-wagon-providers.html"> Guide to Selecting Alternative Wagon Providers</a></li>
<li><a href="./mini/guide-building-jdk14-on-jdk15.html"> Guide to Building JDK 1.4 Projects Using JDK 1.5</a></li>
-<li><a href="./mini/guide-default-execution-ids.html"> Guide to Configuring Default Mojo Executions</a></li></ul>
-<div class="section">
+<li><a href="./mini/guide-default-execution-ids.html"> Guide to Configuring Default Mojo Executions</a></li></ul><section>
<h4><a name="Maven_Tools_and_IDE_Integration"></a>Maven Tools and IDE Integration</h4>
<ul>
-<li><a href="./mini/guide-bash-m2-completion.html">Maven Auto-Completion Using BASH</a></li></ul></div></div>
-<div class="section">
+<li><a href="./mini/guide-bash-m2-completion.html">Maven Auto-Completion Using BASH</a></li></ul></section></section><section>
<h3><a name="Development_Guides"></a>Development Guides</h3>
<ul>
<li><a href="./development/guide-building-maven.html">Building Maven from Scratch</a></li>
<li><a href="./development/guide-maven-development.html">Developing Maven</a></li>
<li><a href="./development/guide-plugin-documentation.html">The Plugin Documentation Standard</a></li>
-<li><a href="./development/guide-documentation-style.html">Maven Documentation Style</a></li></ul></div>
-<div class="section">
+<li><a href="./development/guide-documentation-style.html">Maven Documentation Style</a></li></ul></section><section>
<h3><a name="The_Maven_Community"></a>The Maven Community</h3>
<ul>
<li><a href="../community.html">The Maven Community</a></li>
<li><a href="./development/guide-helping.html">Helping with Maven</a></li>
<li><a href="./mini/guide-new-committers.html">Guide for New Committers</a></li>
<li><a href="./development/guide-testing-development-plugins.html">Testing Development Versions of Plugins</a></li>
-<li><a href="../articles.html">3rd Party Resources</a></li></ul>
-<div class="section">
+<li><a href="../articles.html">3rd Party Resources</a></li></ul><section>
<h4><a name="Conventions"></a>Conventions</h4>
<ul>
<li><a href="../maven-conventions.html">Maven Conventions</a></li>
<li><a href="./mini/guide-naming-conventions.html">Naming Conventions</a></li>
-<li><a href="./mini/guide-using-one-source-directory.html">When You Can't Use the Conventions</a></li></ul></div>
-<div class="section">
+<li><a href="./mini/guide-using-one-source-directory.html">When You Can't Use the Conventions</a></li></ul></section><section>
<h4><a name="The_Central_Repository"></a>The Central Repository</h4>
<ul>
<li><a href="/repository/">Introduction to the Central Repository</a></li>
<li><a href="/repository/guide-central-repository-upload.html">Uploading Artifacts to the Central Repository</a></li>
-<li><a href="/repository/central-metadata.html">Improving the Repository</a></li></ul></div></div>
-<div class="section">
+<li><a href="/repository/central-metadata.html">Improving the Repository</a></li></ul></section></section><section>
<h3><a name="References"></a>References</h3>
<ul>
<li><a href="../pom.html">POM Overview</a> (<a href="../ref/current/maven-model/maven.html">Technical Project Descriptor</a>)</li>
@@ -232,8 +218,7 @@ Eric Redmond" />
<li><a href="../plugins/index.html">Core Plug-ins List</a></li>
<li><a href="../developers/mojo-api-specification.html">Mojo API</a></li>
<li><a href="../glossary.html">Glossary</a></li>
-<li><a href="./MavenQuickReferenceCard.pdf">Maven Quick Reference Card - PDF</a></li></ul></div>
-<div class="section">
+<li><a href="./MavenQuickReferenceCard.pdf">Maven Quick Reference Card - PDF</a></li></ul></section><section>
<h3><a name="Javadoc_API"></a>Javadoc API</h3>
<p>Here is some useful Javadoc API links to the current version of Maven:</p>
<ul>
@@ -243,7 +228,7 @@ Eric Redmond" />
<li><a href="/ref/current/maven-model/apidocs/">Maven Model</a></li>
<li><a href="/ref/current/maven-core/apidocs/">Maven Core</a></li>
<li><a href="/ref/current/maven-settings/apidocs/">Maven Settings</a></li></ul>
-<p>You could also browse the <a href="/ref/current/">full technical documentation references</a> of the current version of Maven.</p></div></div>
+<p>You could also browse the <a href="/ref/current/">full technical documentation references</a> of the current version of Maven.</p></section></section>
</div>
</div>
</div>