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 bu...@apache.org on 2014/07/11 07:10:39 UTC

svn commit: r915746 [9/13] - in /websites/staging/maven/trunk/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/ d...

Modified: websites/staging/maven/trunk/content/guides/mini/guide-new-committers.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-new-committers.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-new-committers.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide for new committers</title>
+    <title>Maven &#x2013; Guide for new committers</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide for new committers
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide for new commiters<a name="Guide_for_new_commiters"></a></h2>
+<h2><a name="Guide_for_new_commiters"></a>Guide for new commiters</h2>
 <p>First thing is to sort out some administrative tasks. Before your account is created and commit access granted you must complete and fax back to Apache the <a class="externalLink" href="http://www.apache.org/licenses/#clas">Committer's License Agreement</a>.</p>
 <p>While this process is sorting itself out it is recommended that you peruse the various guides provided by Apache. All the guides are located in the <a class="externalLink" href="http://www.apache.org/dev/">Development Infrastructure Information</a>.</p>
 <p>Of particular interest is the <a class="externalLink" href="http://www.apache.org/dev/committers.html">Committer's FAQ</a> and the <a class="externalLink" href="http://www.apache.org/dev/new-committers-guide.html">New Committer's Guide</a>.</p>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-proxies.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-proxies.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-proxies.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to using proxies</title>
+    <title>Maven &#x2013; Guide to using proxies</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to using proxies
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Configuring a proxy<a name="Configuring_a_proxy"></a></h2>
+<h2><a name="Configuring_a_proxy"></a>Configuring a proxy</h2>
 <p>You can configure a proxy to use for some or all of your HTTP requests in Maven 2.0. The username and password are only required if your proxy requires basic authentication (note that later releases may support storing your passwords in a secured keystore - in the mean time, please ensure your settings.xml file (usually ${user.home}/.m2/settings.xml) is secured with permissions appropriate for your operating system).</p>
 <p>The <tt>nonProxyHosts</tt> setting accepts wild cards, and each host not to proxy is separated by the | character. This matches the JDK configuration equivalent.</p>
 <div class="source">
@@ -266,7 +266,7 @@
 </pre></div>
 <p>Please note that urrently NTLM proxies are not supported as they have not been tested. You may be able to use the relevant system properties on JDK 1.4+ to make this work.</p>
 <div class="section">
-<h3>Resources<a name="Resources"></a></h3>
+<h3><a name="Resources"></a>Resources</h3>
 <ol style="list-style-type: decimal">
 <li><a href="../../maven-settings/settings.html">Settings descriptor documentation</a></li>
 <li><a href="./guide-configuring-maven.html">Configuring Maven</a></li></ol></div></div>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-releasing.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-releasing.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-releasing.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to using the release plugin</title>
+    <title>Maven &#x2013; Guide to using the release plugin</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
         <meta name="author" content="Jason van Zyl
 Trent Rosenbaum
 Vincent Massol" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Vincent Massol" />
         Guide to using the release plugin
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -243,16 +243,16 @@ Vincent Massol" />
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Releasing<a name="Releasing"></a></h2>
+<h2><a name="Releasing"></a>Releasing</h2>
 <div class="section">
-<h3>Introduction<a name="Introduction"></a></h3>
+<h3><a name="Introduction"></a>Introduction</h3>
 <p>The main aim of the maven-release plugin is to provide a standard mechanism to release project artifacts outside the immediate development team. The plugin provides basic functionality to create a release and to update the project's SCM accordingly.</p>
 <p>To create a release the maven-release plugin is executed through maven in 2 stages:</p>
 <ol style="list-style-type: decimal">
 <li>Preparing the release.</li>
 <li>Performing the release.</li></ol></div>
 <div class="section">
-<h3>Preparing the release<a name="Preparing_the_release"></a></h3>
+<h3><a name="Preparing_the_release"></a>Preparing the release</h3>
 <p>The plugin will record release information into a new revision of the project's <i>pom.xml</i> file as well as applying SCM versioning to the project's resources.</p>
 <p>The <tt>release:prepare</tt> goal will:</p>
 <ol style="list-style-type: decimal">
@@ -349,7 +349,7 @@ Vincent Massol" />
 <p>This value is the placed in the next revision of the <i>pom.xml</i> file used for continuing development. If the current release represented version 1.0 then an appropriate value could be 2.0-SNAPSHOT. The SNAPSHOT designator is required to prepare and perform future releases. This value is then committed in the next development revision of the <i>pom.xml</i> file.</p></li></ul>
 <p>After maven has been supplied with the required information the maven-release plugin will interact with the project's SCM and define a relese to be extracted and deployed. At the same time the project's development trunk is updated allowing developers to continue with further modifications that will be included within future releases.</p></div>
 <div class="section">
-<h3>Performing the release<a name="Performing_the_release"></a></h3>
+<h3><a name="Performing_the_release"></a>Performing the release</h3>
 <p>The plugin will extract file revisions associated with the current release. Maven will compile, test and package the versioned project source code into an artifact. The final deliverable will then be released into an appropriate maven repository.</p>
 <p>The <tt>release:perform</tt> goal will:</p>
 <ol style="list-style-type: decimal">
@@ -410,12 +410,12 @@ checkpoint.check-in-development-version=
 <li><i>artifact id</i>-<i>version</i>.pom
 <p>The contents of the <i>pom.xml</i> file used to create the current release of the project.</p></li></ul></div>
 <div class="section">
-<h3>Troubleshooting<a name="Troubleshooting"></a></h3>
+<h3><a name="Troubleshooting"></a>Troubleshooting</h3>
 <div class="section">
-<h4>I get a &quot;The authenticity of host '<i>host</i>' can't be established.&quot; error and the build hangs<a name="I_get_a_The_authenticity_of_host_host_cant_be_established._error_and_the_build_hangs"></a></h4>
+<h4><a name="I_get_a_The_authenticity_of_host_host_cant_be_established._error_and_the_build_hangs"></a>I get a &quot;The authenticity of host '<i>host</i>' can't be established.&quot; error and the build hangs</h4>
 <p>This is because your <tt>~user/.ssh/known_hosts</tt> file doesn't have the host listed. You'd normally get a prompt to add the host to the known host list but Maven doesn't propagate that prompt. The solution is to add the host the <tt>known_hosts</tt> file before executing Maven. On Windows, this can be done by installing an OpenSSH client (for example <a class="externalLink" href="http://sshwindows.sourceforge.net/download/">SSHWindows</a>), running <tt>ssh &lt;host</tt>&gt; and accepting to add the host.</p></div>
 <div class="section">
-<h4>The site deploy goal hangs<a name="The_site_deploy_goal_hangs"></a></h4>
+<h4><a name="The_site_deploy_goal_hangs"></a>The site deploy goal hangs</h4>
 <p>First, this means that you have successfully deployed the artifacts to the remote repo and that it's only the site deployment that is now an issue. Stop your build, cd to <b>target/checkout</b>&gt; and run the build again by executing <tt>mvn site:deploy</tt>. You should see a prompt asking you to enter a password. This happens if your key is not in the authorized keys on the server.</p></div></div></div>
       </div>
     </div>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-relocation.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-relocation.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-relocation.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to relocation</title>
+    <title>Maven &#x2013; Guide to relocation</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Dennis Lundberg" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to relocation
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide to relocation<a name="Guide_to_relocation"></a></h2>
+<h2><a name="Guide_to_relocation"></a>Guide to relocation</h2>
 <p>Sometimes it is necessary to relocate artifacts in the repository. One example of that is when a project moves from Maven 1 to Maven 2. Maven 1 projects have traditionally used a flat repository structure, while Maven 2 uses a deep repository structure. As an example the Maven 1 project has a groupId of <tt>maven</tt> while the Maven 2 project has a groupId of <tt>org.apache.maven</tt>.</p>
 <p>Making changes to the repository can have far reaching consequences. So it is best to get it right the first time, hence this guide. It will go through a couple of different kinds of relocations:</p>
 <ul>
@@ -250,7 +250,7 @@
 <li>Maven 1 to Maven 2</li></ul>
 <p>The goal of the examples below is to relocate the groupId from <tt>bar</tt> to <tt>org.bar</tt> for the <tt>foo</tt> project.</p>
 <div class="section">
-<h3>How to relocate a Maven 1 artifact to a different groupId<a name="How_to_relocate_a_Maven_1_artifact_to_a_different_groupId"></a></h3>
+<h3><a name="How_to_relocate_a_Maven_1_artifact_to_a_different_groupId"></a>How to relocate a Maven 1 artifact to a different groupId</h3>
 <ol style="list-style-type: decimal">
 <li>Copy all <tt>foo</tt>-related files from <tt>/bar/</tt> in your Maven 1 repository to a temporary location.</li>
 <li>Change the groupId to <tt>org.bar</tt> in all the <tt>foo</tt>-related pom files in the temporary location.</li>
@@ -259,10 +259,10 @@
 <li>If your project syncs with ibiblio, you should now initiate that sync. This might happen automatically depending on your projects sync policy.</li></ol>
 <p>Your <tt>foo</tt>-artifacts are now available to Maven 1 users with both the old and the new groupId.</p>
 <div class="section">
-<h4>Releasing the next version<a name="Releasing_the_next_version"></a></h4>
+<h4><a name="Releasing_the_next_version"></a>Releasing the next version</h4>
 <p>When the next release of <tt>foo</tt> is made, you publish the Maven 1 pom as you have always done. Unfortunately Maven 1 does not have a concept of automatic relocation and notification, so you will have to inform your users of the changed groupId through your regular information channels.</p></div></div>
 <div class="section">
-<h3>How to relocate a Maven 2 artifact to a different groupId<a name="How_to_relocate_a_Maven_2_artifact_to_a_different_groupId"></a></h3>
+<h3><a name="How_to_relocate_a_Maven_2_artifact_to_a_different_groupId"></a>How to relocate a Maven 2 artifact to a different groupId</h3>
 <ol style="list-style-type: decimal">
 <li>Copy all <tt>foo</tt>-related files from <tt>/bar/foo/</tt> in your Maven 2 repository to a temporary location.</li>
 <li>Change the groupId to <tt>org.bar</tt> in all <tt>foo</tt>-related pom files in the temporary location.</li>
@@ -287,16 +287,16 @@
 <li>If your project syncs with ibiblio, you should now initiate that sync. This might happen automatically depending on your projects sync policy.</li></ol>
 <p>Your <tt>foo</tt>-artifacts are now available to Maven 2 users with both the old and the new groupId. Projects using the old groupId will automatically be redirected to the new groupId and a warning telling the user to update their dependencies will be issued.</p>
 <div class="section">
-<h4>Releasing the next version<a name="Releasing_the_next_version"></a></h4>
+<h4><a name="Releasing_the_next_version"></a>Releasing the next version</h4>
 <p>When the next release of <tt>foo</tt> is made, you should publish two Maven 2 pom files. First you should publish a pom with the new groupId <tt>org.bar</tt>.</p>
 <p>Because data in the repository is not supposed to change, Maven 2 doesn't download pom files that it has already downloaded. Therefor you will also need to publish a pom file with the old groupId <tt>bar</tt> for the new version. This should be a minimal relocation pom (as described in step 4 above), but for the new version of <tt>foo</tt>.</p>
 <p>For the release after that, you only need to publish a Maven 2 pom with a groupId of <tt>org.bar</tt>, since users of the previous version have been informed of the changed groupId.</p></div></div>
 <div class="section">
-<h3>How to relocate a Maven 1 artifact to a Maven 2 artifact with a different groupId<a name="How_to_relocate_a_Maven_1_artifact_to_a_Maven_2_artifact_with_a_different_groupId"></a></h3>
+<h3><a name="How_to_relocate_a_Maven_1_artifact_to_a_Maven_2_artifact_with_a_different_groupId"></a>How to relocate a Maven 1 artifact to a Maven 2 artifact with a different groupId</h3>
 <p><i>This is only of interest to organizations (like the Apache Software Foundation) that automatically converts the contents of their Maven 1 repository to their Maven 2 repository.</i></p>
 <p>Follow steps 4 to 6 in the section <i>How to relocate a Maven 2 artifact to a different groupId</i> above.</p>
 <div class="section">
-<h4>Releasing the next version<a name="Releasing_the_next_version"></a></h4>
+<h4><a name="Releasing_the_next_version"></a>Releasing the next version</h4>
 <p>When the next release of <tt>foo</tt> is made, you should publish the Maven 1 pom as you have always done. In addition to that, you should publish a Maven 2 pom with a groupId of <tt>bar</tt>, a version of &lt;next-version&gt; and include a relocation section. This step can be done once for the first release of a project, after the groupId has been changed, but your users will be happier if you do it more times.</p></div></div></div>
       </div>
     </div>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-repository-ssl.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-repository-ssl.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-repository-ssl.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Remote repository access through authenticated HTTPS</title>
+    <title>Maven &#x2013; Remote repository access through authenticated HTTPS</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Arnaud Bailly" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Remote repository access through authenticated HTTPS
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,10 +241,10 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide to Remote repository access through authenticated HTTPS<a name="Guide_to_Remote_repository_access_through_authenticated_HTTPS"></a></h2>
+<h2><a name="Guide_to_Remote_repository_access_through_authenticated_HTTPS"></a>Guide to Remote repository access through authenticated HTTPS</h2>
 <p>This document describes how to configure Maven for accessing a remote repository that sits behind an HTTPS server which requires client authentication with certificates. It is expected that this documentation be valid both for Maven 1.x and Maven 2.0.</p>
 <div class="section">
-<h3>The problem<a name="The_problem"></a></h3>
+<h3><a name="The_problem"></a>The problem</h3>
 <p>You have a server storing a maven repository at addresse <tt>https://my.server.com/maven</tt>. This server only serves clients authenticated through SSL protocol by a valid certificate signed by an approved certificate authority's certificate which we call the <tt>CACert</tt>. In the simplest case where the server is used internally by an identified community of users (eg. corporate intranet), the server's certificate is the certificate authority as the server is used only internally.</p>
 <p>So we assume that we have access to the trusted certificate in X.509 format stored in a file named:</p>
 <div>
@@ -259,13 +259,13 @@
 <div>
 <pre>maven.repo.remote=https://my.server.com/maven,http://www.ibiblio.org/maven</pre></div></div>
 <div class="section">
-<h3>The solution<a name="The_solution"></a></h3>
+<h3><a name="The_solution"></a>The solution</h3>
 <p>For maven to use this repository, we should take the following steps:</p>
 <ol style="list-style-type: decimal">
 <li>Create a store to hold the server's certificate usings Sun's <a class="externalLink" href="http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/keytool.html"> keytool</a>,</li>
 <li>Defines properties to be used by HttpClient for finding keys and certificate</li></ol>
 <div class="section">
-<h4>Storing certificate<a name="Storing_certificate"></a></h4>
+<h4><a name="Storing_certificate"></a>Storing certificate</h4>
 <p>The following command line imports the certififcate authority's certificate into a JKS formatted key store named <tt>trust.jks</tt>, the <i>trust store</i>.</p>
 <div>
 <pre>$&gt; keytool -v -alias mavensrv -import \
@@ -285,7 +285,7 @@ Certificate was added to keystore
 $&gt;</pre></div>
 <p>Note that it should be possible to import a full chain of certificates with only one root certificate being trusted but the author did not test it.</p></div>
 <div class="section">
-<h4>Setting properties<a name="Setting_properties"></a></h4>
+<h4><a name="Setting_properties"></a>Setting properties</h4>
 <p>The following properties must be set at start of maven to be accessible when HttpClient starts up.</p>
 <dl>
 <dt>javax.net.ssl.trustStore</dt>
@@ -302,7 +302,7 @@ $&gt;</pre></div>
 <dd>the password protecting the store</dd></dl>
 <p>Not all the properties must be set depending of your precise settings: type of store may left to default, password may be empty.</p>
 <div class="section">
-<h5>Maven 2.0<a name="Maven_2.0"></a></h5>
+<h5><a name="Maven_2.0"></a>Maven 2.0</h5>
 <p>They may be set either on maven's command-line, in <tt>.mavenrc</tt> file or in <tt>MAVEN_OPTS</tt> environment variable. For the setting defined in this document, here is an example <tt>.mavenrc</tt> file:</p>
 <div>
 <pre>MAVEN_OPTS=&quot;-Xmx512m -Djavax.net.ssl.trustStore=trust.jks \
@@ -311,10 +311,10 @@ $&gt;</pre></div>
                      -Djavax.net.ssl.keyStoreType=pkcs12 \
                      -Djavax.net.ssl.keyStorePassword=XXXXXX&quot;</pre></div></div>
 <div class="section">
-<h5>For maven 1.X users<a name="For_maven_1.X_users"></a></h5>
+<h5><a name="For_maven_1.X_users"></a>For maven 1.X users</h5>
 <p>Setting these properties in <tt>build.properties</tt> or <tt>project.properties</tt> does <b>not work</b>: the properties are needed before any of theses files are opened.</p></div></div></div>
 <div class="section">
-<h3>Links<a name="Links"></a></h3>
+<h3><a name="Links"></a>Links</h3>
 <p>The following links may be useful in understanding SSL infrastructure management in Java:</p>
 <ul>
 <li><a class="externalLink" href="http://java.sun.com/j2se/1.4.2/docs/guide/security/"> Javasecurity infrastructure (1.4.2)</a></li>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-site.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-site.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-site.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to creating a site</title>
+    <title>Maven &#x2013; Guide to creating a site</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -14,7 +14,7 @@
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Brett Porter
 Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@ Jason van Zyl" />
         Guide to creating a site
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -242,9 +242,9 @@ Jason van Zyl" />
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Creating a site<a name="Creating_a_site"></a></h2>
+<h2><a name="Creating_a_site"></a>Creating a site</h2>
 <div class="section">
-<h3>Creating Content<a name="Creating_Content"></a></h3>
+<h3><a name="Creating_Content"></a>Creating Content</h3>
 <p>The first step to creating your site is to create some content. In Maven 2.0, the site content is separated by format, as there are several available.</p>
 <div>
 <pre>+- src/
@@ -267,17 +267,17 @@ Jason van Zyl" />
 <p>Other formats are available, but at this point these 3 are the best tested. There are also several possible output formats, but as of 2.0, only XHTML is available.</p>
 <p>Note that all of the above is optional - just one index file is required in one of the input trees. Each of the paths will be merged together to form the root directory of the site.</p></div>
 <div class="section">
-<h3>Customizing the Look &amp; Feel<a name="Customizing_the_Look__Feel"></a></h3>
+<h3><a name="Customizing_the_Look__Feel"></a>Customizing the Look &amp; Feel</h3>
 <p>If you want to tune the way your site looks, you can use a custom skin to provide your own CSS styles. If that is still not enough, you can even tweak the output templates that Maven uses to generate the site documentation. You can visit the <a class="externalLink" href="http://maven.apache.org/skins/">Skins site</a> to have a look at some of the skins that you can use to change the look of your site.</p><!-- TODO: The following link is currently not available. Restore it when it becomes available again. --><!-- For an in-depth discussion of site customization, please have a look at the --><!-- {{{http://www.sonatype.com/book/site-generation.html} Maven User Guide, Chapter 9, "Site Generation"}}. --></div>
 <div class="section">
-<h3>Generating the Site<a name="Generating_the_Site"></a></h3>
+<h3><a name="Generating_the_Site"></a>Generating the Site</h3>
 <p>Generating the site is very simple, and fast!</p>
 <div>
 <pre>mvn site</pre></div>
 <p>By default, the resulting site will be in <tt>target/site/...</tt></p>
 <p>For more information on the Maven Site Plugin, see its <a href="../../plugins/maven-site-plugin/"> plugin reference</a>.</p></div>
 <div class="section">
-<h3>Deploying the Site<a name="Deploying_the_Site"></a></h3>
+<h3><a name="Deploying_the_Site"></a>Deploying the Site</h3>
 <p>To be able to deploy the site, you must first declare a location to distribute to in your <tt>pom.xml</tt>, similar to the repository for deployment.</p>
 <div>
 <pre>&lt;project&gt;
@@ -296,7 +296,7 @@ Jason van Zyl" />
 <div>
 <pre>mvn site-deploy</pre></div></div>
 <div class="section">
-<h3>Creating a Site Descriptor<a name="Creating_a_Site_Descriptor"></a></h3>
+<h3><a name="Creating_a_Site_Descriptor"></a>Creating a Site Descriptor</h3>
 <p>The <tt>site.xml</tt> file is used to describe the layout of the site, and replaces the <tt>navigation.xml</tt> file used in Maven 1.x.</p>
 <p>A sample is given below:</p>
 <div>
@@ -334,7 +334,7 @@ Jason van Zyl" />
 <p><b>Note:</b> The <tt>&lt;menu ref=&quot;reports&quot;/&gt;</tt> element above. When building the site, this is replaced by a menu with links to all the reports that you have configured.</p>
 <p>More information about the site descriptor is available at the site for the <a class="externalLink" href="http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html">Maven Site Plugin</a>.</p></div>
 <div class="section">
-<h3>Adding Extra Resources<a name="Adding_Extra_Resources"></a></h3>
+<h3><a name="Adding_Extra_Resources"></a>Adding Extra Resources</h3>
 <p>You can add any arbitrary resource to your site by including them in a <tt>resources</tt> directory as shown below. Additional CSS files will be picked up when they are placed in the <tt>css</tt> directory within the <tt>resources</tt> directory.</p>
 <div>
 <pre>+- src/
@@ -348,7 +348,7 @@ Jason van Zyl" />
 <p>The file <tt>site.css</tt> will be added to the default XHTML output, so it can be used to adjust the default Maven stylesheets if desired.</p>
 <p>The file <tt>pic1.jpg</tt> will be available via a relative reference to the <tt>images</tt> directory from any page in your site.</p></div>
 <div class="section">
-<h3>Configuring Reports<a name="Configuring_Reports"></a></h3>
+<h3><a name="Configuring_Reports"></a>Configuring Reports</h3>
 <p>Maven has several reports that you can add to your web site to display the current state of the project. These reports take the form of plugins, just like those used to build the project.</p>
 <p>There are many standard reports that are available by gleaning information from the POM. Currently what is provided by default are:</p>
 <ul>
@@ -378,7 +378,7 @@ Jason van Zyl" />
 <p>If you have included the appropriate <tt>&lt;menu ref=&quot;reports&quot;/&gt;</tt> tag in your <tt>site.xml</tt> descriptor, then when you regenerate the site those items will appear in the menu.</p>
 <p><b>Note:</b> Many report plugins provide a parameter called <tt>outputDirectory</tt> or similar to specify the destination for their report outputs. This parameter is only relevant if the report plugin is run standalone, i.e. by invocation directly from the command line. In constrast, when reports are generated as part of the site, the configuration of the Maven Site Plugin will determine the effective output directory to ensure that all reports end up in a central location.</p><!-- TODO: explain report sets --></div>
 <div class="section">
-<h3>Internationalization<a name="Internationalization"></a></h3>
+<h3><a name="Internationalization"></a>Internationalization</h3>
 <p>Internationalization in Maven is very simple, as long as the reports you are using have that particular locale defined. For an overview of supported languages and instructions on how to add further languages, please see the related article <a href="../../plugins/maven-site-plugin/i18n.html"> Internationalization</a> from the Maven Site Plugin.</p>
 <p>To enable multiple locales, add a configuration similar to the following to your POM:</p>
 <div>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-snippet-macro.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to the Snippet Macro</title>
+    <title>Maven &#x2013; Guide to the Snippet Macro</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Wendy Smoak" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to the Snippet Macro
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/references/apt-
 format.html --><div class="section">
-<h2>Guide to the Snippet Macro<a name="Guide_to_the_Snippet_Macro"></a></h2>
+<h2><a name="Guide_to_the_Snippet_Macro"></a>Guide to the Snippet Macro</h2>
 <p>When generating your project website with Maven, you have the option of dynamically including <i>snippet</i>s of source code in your pages.</p>
 <p>A <i>snippet</i> is a section of a source code file that is surrounded by specially formatted comments.</p>
 <p>This functionality is inspired by the <a class="externalLink" href="http://www.atlassian.com/software/confluence/">Confluence</a> snippet macro, and is provided by the Maven Doxia project by way of the Maven Site Plugin.</p>
@@ -250,9 +250,9 @@
 <p>Following are examples of snippets in various source documents, as well as the corresponding macros in the APT documentation format.</p>
 <p>See the Doxia <a class="externalLink" href="http://maven.apache.org/doxia/macros/index.html#Snippet_Macro">Macros Guide</a> for more information and examples.</p>
 <div class="section">
-<h3>Snippets in Sources<a name="Snippets_in_Sources"></a></h3>
+<h3><a name="Snippets_in_Sources"></a>Snippets in Sources</h3>
 <div class="section">
-<h4>Java<a name="Java"></a></h4>
+<h4><a name="Java"></a>Java</h4>
 <div>
 <pre>    // START SNIPPET: snip-id
     public static void main( String[] args )
@@ -261,7 +261,7 @@
     }
     // END SNIPPET: snip-id</pre></div></div>
 <div class="section">
-<h4>XML<a name="XML"></a></h4>
+<h4><a name="XML"></a>XML</h4>
 <div>
 <pre>  &lt;!-- START SNIPPET: snip-id --&gt;
   &lt;navigation-rule&gt;
@@ -273,7 +273,7 @@
   &lt;/navigation-rule&gt;
   &lt;!-- END SNIPPET: snip-id --&gt;</pre></div></div>
 <div class="section">
-<h4>JSP<a name="JSP"></a></h4>
+<h4><a name="JSP"></a>JSP</h4>
 <div>
 <pre>  &lt;%-- START SNIPPET: snip-id --%&gt;
   &lt;ul&gt;
@@ -282,9 +282,9 @@
   &lt;/ul&gt;
   &lt;%-- END SNIPPET: snip-id --%&gt;</pre></div></div></div>
 <div class="section">
-<h3>Snippets in Documentation<a name="Snippets_in_Documentation"></a></h3>
+<h3><a name="Snippets_in_Documentation"></a>Snippets in Documentation</h3>
 <div class="section">
-<h4>APT<a name="APT"></a></h4>
+<h4><a name="APT"></a>APT</h4>
 <div>
 <pre> %{snippet|id=snip-id|url=http://svn.example.com/path/to/Sample.java}
 

Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-ant.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-ant.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-ant.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to using Ant with Maven</title>
+    <title>Maven &#x2013; Guide to using Ant with Maven</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to using Ant with Maven
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide to using Ant with Maven<a name="Guide_to_using_Ant_with_Maven"></a></h2>
+<h2><a name="Guide_to_using_Ant_with_Maven"></a>Guide to using Ant with Maven</h2>
 <p>The example above illustrates how to bind an ant script to a lifecycle phase. You can add a script to each lifecycle phase, by duplicating the <i>execution/</i> section and specifying a new phase.</p>
 <div class="source">
 <pre>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-extensions.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-extensions.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-extensions.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to using Extensions</title>
+    <title>Maven &#x2013; Guide to using Extensions</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to using Extensions
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,10 +241,10 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Using Extensions<a name="Using_Extensions"></a></h2>
+<h2><a name="Using_Extensions"></a>Using Extensions</h2>
 <p>Extensions are used to enable Wagon providers, used for the transport of artifact between repositories, and plug-ins which provide lifecycle enhancements.</p>
 <div class="section">
-<h3>Wagon providers<a name="Wagon_providers"></a></h3>
+<h3><a name="Wagon_providers"></a>Wagon providers</h3>
 <div class="source">
 <pre>
 &lt;project&gt;
@@ -264,7 +264,7 @@
 <p><i>Note:</i> Wagon 1.0-beta-3+ requires Maven 2.1.0 or above. For Maven 2.0.10 and earlier, use Wagon 1.0-beta-2.</p>
 <p><i>Note:</i> Some Wagons require JDK 5.0 to operate correctly.</p></div>
 <div class="section">
-<h3>Plug-ins which provide lifecycle enhancements<a name="Plug-ins_which_provide_lifecycle_enhancements"></a></h3>
+<h3><a name="Plug-ins_which_provide_lifecycle_enhancements"></a>Plug-ins which provide lifecycle enhancements</h3>
 <div class="source">
 <pre>
 &lt;project&gt;

Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-m1-repos-with-m2.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-m1-repos-with-m2.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-m1-repos-with-m2.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to using Maven 1.x repositories with Maven 2.x</title>
+    <title>Maven &#x2013; Guide to using Maven 1.x repositories with Maven 2.x</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to using Maven 1.x repositories with Maven 2.x
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide to using Maven 1.x repositories with Maven 2.x<a name="Guide_to_using_Maven_1.x_repositories_with_Maven_2.x"></a></h2>
+<h2><a name="Guide_to_using_Maven_1.x_repositories_with_Maven_2.x"></a>Guide to using Maven 1.x repositories with Maven 2.x</h2>
 <p>When you are migrating from Maven 1.x to Maven 2.x you will first be trying to convert your build and to make this easier we have provided a way for you to use your existing Maven 1.x repository so that you don't have to convert your repository before trying to migrate your projects. To use a Maven 1.x repository with your Maven 2.x project you need to specify this in your POM as follows:</p>
 <div class="source">
 <pre>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to using Modello</title>
+    <title>Maven &#x2013; Guide to using Modello</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
         <meta name="author" content="Jason van Zyl
 Hervé Boutemy" />
         <meta name="Date-Creation-yyyymmdd" content="20090301" />
-    <meta name="Date-Revision-yyyymmdd" content="20140701" />
+    <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Hervé Boutemy" />
         Guide to using Modello
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -243,7 +243,7 @@ Hervé Boutemy" />
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide to using Modello<a name="Guide_to_using_Modello"></a></h2>
+<h2><a name="Guide_to_using_Modello"></a>Guide to using Modello</h2>
 <p><a class="externalLink" href="http://modello.codehaus.org/index.html">Modello</a> is a tool for generating resources from a simple model. From a simple model you can generate things like:</p>
 <ul>
 <li>Java sources</li>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-one-source-directory.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-one-source-directory.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-one-source-directory.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to Using Maven when You Can't Use the Conventions</title>
+    <title>Maven &#x2013; Guide to Using Maven when You Can't Use the Conventions</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Brett Porter" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to Using Maven when You Can't Use the Conventions
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,33 +241,33 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Using Maven When You Can't Use the Conventions<a name="Using_Maven_When_You_Cant_Use_the_Conventions"></a></h2>
+<h2><a name="Using_Maven_When_You_Cant_Use_the_Conventions"></a>Using Maven When You Can't Use the Conventions</h2>
 <p>There is a common misconception that Maven can't build a project that doesn't conform to certain directory structures or build practices. This often isn't the case - however it is true that some Maven features or plugins (especially by third parties) may not work or work completely.</p>
 <p>This guide will help you set up Maven on your project when the directive from on high is to not change the existing layout, and detail some of the feature that you might miss when doing so.</p>
 <p><i>The Maven developers highly recommend you use this as a last resort. There are good reasons why the defaults are the way they are, and we strongly recommend you use them if you can. It encourages consistency and means one less thing you ever need to worry about when starting a new project - there are more interesting things to do then change your layout for the sake of it! Hopefully having used any of these techniques you find that Maven proves itself capable, you will reconsider restructuring to address these issues.</i></p>
 <div class="section">
-<h3>Using Multiple Source Directories<a name="Using_Multiple_Source_Directories"></a></h3>
+<h3><a name="Using_Multiple_Source_Directories"></a>Using Multiple Source Directories</h3>
 <p>This occurs when you are producing a single JAR (or other artifact), and have several source directories with classes you want to include.</p>
 <div class="section">
-<h4>Why isn't this recommended?<a name="Why_isnt_this_recommended"></a></h4>
+<h4><a name="Why_isnt_this_recommended"></a>Why isn't this recommended?</h4>
 <p>...</p><!-- TODO --></div>
 <div class="section">
-<h4>How do I do this?<a name="How_do_I_do_this"></a></h4>
+<h4><a name="How_do_I_do_this"></a>How do I do this?</h4>
 <p>...</p><!-- TODO --></div>
 <div class="section">
-<h4>What are the limitations?<a name="What_are_the_limitations"></a></h4>
+<h4><a name="What_are_the_limitations"></a>What are the limitations?</h4>
 <p>There should be no limitations in this approach. Maven natively supports multiple source directories for the purposes of generated sources.</p></div></div>
 <div class="section">
-<h3>Producing Multiple Unique JARs from a Single Source Directory<a name="Producing_Multiple_Unique_JARs_from_a_Single_Source_Directory"></a></h3>
+<h3><a name="Producing_Multiple_Unique_JARs_from_a_Single_Source_Directory"></a>Producing Multiple Unique JARs from a Single Source Directory</h3>
 <p>As many people that complain about not being able to spread out their sources into multiple source directories seem to complain about not wanting to spread anything out, producing several unique artifacts from a single directory using includes and excludes.</p>
 <div class="section">
-<h4>Why isn't this recommended?<a name="Why_isnt_this_recommended"></a></h4>
+<h4><a name="Why_isnt_this_recommended"></a>Why isn't this recommended?</h4>
 <p>This practice can be confusing and risky.</p>
 <ul>
 <li>You may end up building two JARs that include the same classes - this indicates that the common functionality should have been abstracted into a separate dependency.</li>
 <li>You may end up introducing a dependency between the two JARs that you didn't realise, and often a circular dependency. This indicates that the classes are in the wrong JAR, or perhaps that everything should just be a single JAR.</li></ul></div>
 <div class="section">
-<h4>How do I do this?<a name="How_do_I_do_this"></a></h4>
+<h4><a name="How_do_I_do_this"></a>How do I do this?</h4>
 <p>You still should adhere to producing one artifact per POM, but this requires having multiple POMs, and hence multiple subdirectories. The positive to this is that these introduced directories won't change the layout of existing code, and will establish a future layout should you decide to separate.</p>
 <p>Here is an example of setting it up when there is a project with two JARs produced: <tt>core</tt> and <tt>module</tt>.</p>
 <p>You might like to review the <a href="../getting-started/"> Getting Started Guide</a></p><!-- or {{{guide-multi-module.html} Guide to Using Multiple Modules}} -->
@@ -341,10 +341,10 @@
    +- target/
       +- my-module-1.0-SNAPSHOT.jar</pre></div></div>
 <div class="section">
-<h4>What are the limitations?<a name="What_are_the_limitations"></a></h4>
+<h4><a name="What_are_the_limitations"></a>What are the limitations?</h4>
 <p>There is no universal inclusion/exclusion specification, so each plugin needs to be configured individually, and some might not have that capability. In particular, expect that site reports may include all sources, for example.</p></div></div>
 <div class="section">
-<h3>Producing Multiple JARs from a single POM<a name="Producing_Multiple_JARs_from_a_single_POM"></a></h3>
+<h3><a name="Producing_Multiple_JARs_from_a_single_POM"></a>Producing Multiple JARs from a single POM</h3>
 <p>Source directories aside, sometimes people desire to produce multiple JARs from a single POM. Depending on your use case, Maven can support this.</p>
 <ul>
 <li>If you are looking to produce JARs that are different (ie, they have their own dependencies and metadata), Maven doesn't support this. This usually is only needed when sharing a source directory for intrinsically different things, so the use case above applies instead.</li>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to Using Toolchains</title>
+    <title>Maven &#x2013; Guide to Using Toolchains</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Maria Odea Ching" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to Using Toolchains
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,9 +241,9 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/references/apt-
 format.html --><div class="section">
-<h2>Guide to Using Toolchains<a name="Guide_to_Using_Toolchains"></a></h2>
+<h2><a name="Guide_to_Using_Toolchains"></a>Guide to Using Toolchains</h2>
 <div class="section">
-<h3>What is Toolchains?<a name="What_is_Toolchains"></a></h3>
+<h3><a name="What_is_Toolchains"></a>What is Toolchains?</h3>
 <p>The Maven Toolchains provide a way for plugins to discover what JDK (or other tools) are to be used during the build, without the need to configure them. With toolchains, a project can now be built using a specific version of JDK independent from the one Maven is running with. (Think how JDK versions can be set in IDEs like Idea, NetBeans and Eclipse)</p>
 <p>Toolchains would only work in Maven 2.0.9 and higher versions. For more details about it's design and implementation, please see <a class="externalLink" href="http://cwiki.apache.org/confluence/display/MAVENOLD/Toolchains">Toolchains</a>.</p>
 <p>Below are the plugins which are toolchain-aware, meaning they can be used with toolchains:</p>
@@ -253,7 +253,7 @@
 <li><tt>maven-surefire-plugin-2.5</tt></li>
 <li><tt>exec-maven-plugin-1.1.1</tt> (Codehaus MOJO)</li></ol></div>
 <div class="section">
-<h3>Using Toolchains in Your Project<a name="Using_Toolchains_in_Your_Project"></a></h3>
+<h3><a name="Using_Toolchains_in_Your_Project"></a>Using Toolchains in Your Project</h3>
 <p>There are two essential components that you need to configure in order to use toolchains. These are the <tt><a class="externalLink" href="http://maven.apache.org/plugins/maven-toolchains-plugin/">maven-toolchains-plugin</a></tt> and the <tt>toolchains.xml</tt> file.</p>
 <p>The <tt>maven-toolchains-plugin</tt> is the one that sets the toolchain to be used by the toolchain-aware plugins in your project. For example, you want to use a different JDK version to build your project. You can configure the version you want to use via this plugin as shown in the <tt>pom.xml</tt> below.</p>
 <div>

Modified: websites/staging/maven/trunk/content/guides/mini/guide-wagon-providers.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-wagon-providers.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-wagon-providers.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to Selecting Alternative Wagon Providers</title>
+    <title>Maven &#x2013; Guide to Selecting Alternative Wagon Providers</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="John Casey" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to Selecting Alternative Wagon Providers
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,19 +241,19 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Guide to Selecting Alternative Wagon Providers<a name="Guide_to_Selecting_Alternative_Wagon_Providers"></a></h2>
+<h2><a name="Guide_to_Selecting_Alternative_Wagon_Providers"></a>Guide to Selecting Alternative Wagon Providers</h2>
 <p>By default, Maven uses the <tt>java.net.URLConnection</tt> (<tt>HttpURLConnection</tt>) classes provided with the JDK to access repositories that use the HTTP/HTTPs protocols. Unfortunately, since this implementation contains certain bugs, Maven users may find themselves unable to connect to servers that demand some configurations. A couple examples of weird behavior include line-wrapping the Authorization header's Base64 value when passwords are long, and using cached values in preemptive authentication for successive connections to the same server.</p>
 <p>Maven 2.2.0 attempted to amend this problem by switching over to a Wagon implementation that's based on Apache HttpClient. Unfortunately, it soon became apparent that HttpClient doesn't support NTLM (at least, version 2), which effectively means users behind NTLMv2 proxies cannot use Maven 2.2.0.</p>
 <p>To hopefully resolve this once and for all, Maven 2.2.1 will contain support for specifying which Wagon provider you want to use for a given protocol during the build. The provider name will then be appended to the protocol using the format <tt>&lt;protocol&gt;-&lt;provider&gt;</tt> to form the component role-hint for the Wagon.</p>
 <p>As of Maven 2.2.1, there are two ways to specify which Wagon provider should be used: via the command line, or in the <tt>&lt;server&gt;</tt> configuration section of the <tt>settings.xml</tt>.</p>
 <div class="section">
-<h3>Command-Line Configuration<a name="Command-Line_Configuration"></a></h3>
+<h3><a name="Command-Line_Configuration"></a>Command-Line Configuration</h3>
 <p>To specify the Wagon provider from the command line, simply use the <tt>-Dmaven.wagon.provider.&lt;protocol&gt;=&lt;provider-name&gt;</tt> command-line option, like the following:</p>
 <div class="source">
 <pre>mvn -Dmaven.wagon.provider.http=httpclient clean install</pre></div>
 <p>This instructs Maven to use the HttpClient-based Wagon implementation for connections to HTTP repositories.</p></div>
 <div class="section">
-<h3><tt>settings.xml</tt> Configuration<a name="settings.xml_Configuration"></a></h3>
+<h3><a name="settings.xml_Configuration"></a><tt>settings.xml</tt> Configuration</h3>
 <p>To specify which Wagon provider to use for a particular server, modify your <tt>settings.xml</tt> file to add the <tt>&lt;wagonProvider&gt;</tt> configuration to your <tt>&lt;server&gt;</tt> entry, like the following:</p>
 <div class="source">
 <pre>&lt;settings&gt;
@@ -267,7 +267,7 @@
       &lt;/configuration&gt;
     &lt;/server&gt;</pre></div></div>
 <div class="section">
-<h3>Available Wagon Providers<a name="Available_Wagon_Providers"></a></h3>
+<h3><a name="Available_Wagon_Providers"></a>Available Wagon Providers</h3>
 <p>Maven 2.2.1 provides two providers for HTTP/HTTPS Wagons: <tt>lightweight</tt> and <tt>httpclient</tt>. If you add a new HTTP Wagon implementation via build extension, you'll need to make sure the extension binds its Wagon components to role-hints of the form <tt>&lt;protocol&gt;-&lt;provider&gt;</tt> in order to allow users to specify your alternative Wagon provider. For instance, the HttpClient HTTP Wagon component definition looks like this:</p>
 <div class="source">
 <pre>&lt;component&gt;

Modified: websites/staging/maven/trunk/content/guides/mini/guide-webapp.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-webapp.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-webapp.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to Webapps</title>
+    <title>Maven &#x2013; Guide to Webapps</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Guide to Webapps
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>

Modified: websites/staging/maven/trunk/content/guides/mini/index.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/index.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/index.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Maven Mini Guides</title>
+    <title>Maven &#x2013; Maven Mini Guides</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
     </style>
     <link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
         <meta name="author" content="Jason van Zyl" />
-        <meta name="Date-Revision-yyyymmdd" content="20140701" />
+        <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
         Maven Mini Guides
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -241,7 +241,7 @@
     <div id="bodyColumn">
       <div id="contentBox">
         <div class="section">
-<h2>Maven Mini Guides<a name="Maven_Mini_Guides"></a></h2></div>
+<h2><a name="Maven_Mini_Guides"></a>Maven Mini Guides</h2></div>
       </div>
     </div>
     <div class="clear">

Modified: websites/staging/maven/trunk/content/guides/plugin/guide-ant-plugin-development.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/plugin/guide-ant-plugin-development.html (original)
+++ websites/staging/maven/trunk/content/guides/plugin/guide-ant-plugin-development.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
  | Rendered using Apache Maven Stylus Skin 1.5
 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Maven - Guide to Developing Ant Plugins</title>
+    <title>Maven &#x2013; Guide to Developing Ant Plugins</title>
     <style type="text/css" media="all">
       @import url("../../css/maven-base.css");
       @import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
         <meta name="author" content="John Casey
 Dennis Lundberg" />
         <meta name="Date-Creation-yyyymmdd" content="20101217" />
-    <meta name="Date-Revision-yyyymmdd" content="20140701" />
+    <meta name="Date-Revision-yyyymmdd" content="20140711" />
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
                                                     
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Dennis Lundberg" />
         Guide to Developing Ant Plugins
         </div>
             <div class="xright">        
-                                    Last Published: 2014-07-01
+                                    Last Published: 2014-07-11
             </div>
       <div class="clear">
         <hr/>
@@ -243,19 +243,19 @@ Dennis Lundberg" />
     <div id="bodyColumn">
       <div id="contentBox">
         <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/references/apt-
 format.html --><!-- NOTE: This guide has been adapted from "Guide to Developing Java Plugins" --><!-- by Bob Allison. --><div class="section">
-<h2>Developing Ant Plugins for Maven 2.x<a name="Developing_Ant_Plugins_for_Maven_2.x"></a></h2>
+<h2><a name="Developing_Ant_Plugins_for_Maven_2.x"></a>Developing Ant Plugins for Maven 2.x</h2>
 <div class="section">
-<h3>Warning<a name="Warning"></a></h3>
+<h3><a name="Warning"></a>Warning</h3>
 <p><b>The documentation below assumes that you have updated your locally cached cached copy of the maven-plugin-plugin. To update your copy, you will need to include the -U option when you build your plugin project:</b></p>
 <div class="source">
 <pre>mvn -U clean install</pre></div>
 <p>The maven-plugin-plugin is responsible for reading plugin metadata in its various forms and writing a standard Maven plugin descriptor based on the input. It was designed to accommodate multiple plugin languages side by side, but its initial design was slightly flawed for plugin languages that don't include the metadata inline with the source (within the same file). Since the 2.0.1 release of Maven, the maven-plugin-plugin has contained revisions to handle this scenario. Since the API has changed (in a backward-compatible way), and since the Ant plugin support requires these changes be in place, you will see an <tt>AbstractMethodError</tt> if you try to build an Ant-based plugin using the old maven-plugin-plugin.</p></div>
 <div class="section">
-<h3>Introduction<a name="Introduction"></a></h3>
+<h3><a name="Introduction"></a>Introduction</h3>
 <p>The intent of this document is to help users learn to develop Maven plugins using Ant.</p>
 <p>As of the 2.0.1 release, Maven supports Ant-driven plugins. These plugins allow the invocation of Ant targets (specified in scripts embedded in the plugin JAR) at specific points in the build lifecycle. They can also inject parameter values into the Ant project instances when a target is called.</p></div>
 <div class="section">
-<h3>Conventions<a name="Conventions"></a></h3>
+<h3><a name="Conventions"></a>Conventions</h3>
 <p>In this guide, we'll use the standard Maven directory structure for projects, to keep our POMs as simple as possible. It's important to note that this is only a standard layout, not a requirement. The important locations for our discussion are the following:</p>
 <div class="source">
 <pre>  /&lt;project-root&gt;
@@ -270,13 +270,13 @@ Dennis Lundberg" />
   |  |  |  |
   ...</pre></div></div>
 <div class="section">
-<h3>Getting Started<a name="Getting_Started"></a></h3>
+<h3><a name="Getting_Started"></a>Getting Started</h3>
 <p>We'll start with the simplest of all possible plugins. This plugin takes no parameters, and will simply print a message out to the screen when invoked. This should familiarize the reader with the basics of mapping Ant build scripts to the Maven plugin framework. From there, we will gradually increase the complexity of our plugin, adding parameters, interacting with standard project locations, and binding to lifecycle phases. Finally, we'll see how a single Ant build script can be mapped to multiple Maven mojos within the same plugin.</p>
 <div class="section">
-<h4>Hello, World<a name="Hello_World"></a></h4>
+<h4><a name="Hello_World"></a>Hello, World</h4>
 <p>Our first plugin will simply print &quot;Hello, World&quot; to the console.</p>
 <div class="section">
-<h5>The Build Script<a name="The_Build_Script"></a></h5>
+<h5><a name="The_Build_Script"></a>The Build Script</h5>
 <p>The elemental Ant-driven mojo consists of a simple Ant build script, a mapping metadata file, and of course the plugin's POM. If our goal is to print &quot;Hello, World&quot;, we might use an Ant build script that looks something like this:</p>
 <div class="source">
 <pre>hello.build.xml:
@@ -288,7 +288,7 @@ Dennis Lundberg" />
   &lt;/target&gt;
 &lt;/project&gt;</pre></div></div>
 <div class="section">
-<h5>The Mapping Document<a name="The_Mapping_Document"></a></h5>
+<h5><a name="The_Mapping_Document"></a>The Mapping Document</h5>
 <p>Once we've created this build script, we need to tell Maven how to use it as a plugin. This involves creating a mapping document. Note that where the build script was named <b>hello.build.xml</b>, the mapping document is named <b>hello.mojos.xml</b>. The naming of these files is very important, as this is how the plugin parser matches mapping documents to build scripts. It has the general form:</p>
 <ul>
 <li><i>basename</i><b>.build.xml</b> - The Ant build script.</li>
@@ -312,7 +312,7 @@ Dennis Lundberg" />
   &lt;/mojos&gt;
 &lt;/pluginMetadata&gt;</pre></div></div>
 <div class="section">
-<h5>The POM<a name="The_POM"></a></h5>
+<h5><a name="The_POM"></a>The POM</h5>
 <p>Now that we have the build script and mapping document, we're ready to build this plugin. However, in order to build, we need to provide a POM for our new plugin. As it turns out, the POM required for an Ant-driven plugin is fairly complex. This is because we have to configure the maven-plugin-plugin to use the Ant plugin parsing tools in addition to the defaults (such as the Java parsing tools). Our POM might look something like this:</p>
 <div class="source">
 <pre>pom.xml:
@@ -367,7 +367,7 @@ Dennis Lundberg" />
   &lt;/build&gt;
 &lt;/project&gt;</pre></div></div>
 <div class="section">
-<h5>Build It and Run It<a name="Build_It_and_Run_It"></a></h5>
+<h5><a name="Build_It_and_Run_It"></a>Build It and Run It</h5>
 <p>Once we have a POM for our new plugin, we can install it into the local repository just as we would any other Maven project:</p>
 <div class="source">
 <pre>mvn install</pre></div>
@@ -378,11 +378,11 @@ Dennis Lundberg" />
 <div class="source">
 <pre>[echo] Hello, World</pre></div></div></div></div>
 <div class="section">
-<h3>Using <b>prefix:mojo</b> Invocation Syntax<a name="Using_prefix:mojo_Invocation_Syntax"></a></h3>
+<h3><a name="Using_prefix:mojo_Invocation_Syntax"></a>Using <b>prefix:mojo</b> Invocation Syntax</h3>
 <p>Our new plugin works, but look at that command line... The next thing is to configure Maven so we can use the familiar <b>prefix:mojo</b> invocation syntax, and leave that verbose, fully-qualified mess behind.</p>
 <p>As you know, Maven maps plugins to user-friendly prefixes. However, these prefixes might overlap; that is, multiple plugins may try to use the same prefix inadvertently. To avoid the obvious ambiguity associated with such a collision, Maven will search a predetermined list of plugin groupIds for a given prefix, with the first match winning. So, if we want to add our new plugin to this search, we need to configure the list of plugin groupIds.</p>
 <div class="section">
-<h4>Configuring Plugin-Prefix Searching<a name="Configuring_Plugin-Prefix_Searching"></a></h4>
+<h4><a name="Configuring_Plugin-Prefix_Searching"></a>Configuring Plugin-Prefix Searching</h4>
 <p>In order to reference our new plugin by prefix, we need to add its groupId to the <tt>&lt;pluginGroups/&gt;</tt> list in the <tt>settings.xml</tt> file. As you probably know, this file is usually found under $HOME/.m2. The added section to make our plugin's groupId searchable should look like this:</p>
 <div class="source">
 <pre>~/.m2/settings.xml:
@@ -400,15 +400,15 @@ Dennis Lundberg" />
   .
 &lt;/settings&gt;</pre></div></div>
 <div class="section">
-<h4>Run It<a name="Run_It"></a></h4>
+<h4><a name="Run_It"></a>Run It</h4>
 <p>We can check that this worked by invoking our new mojo once again, this time using the prefix syntax:</p>
 <div class="source">
 <pre>mvn hello:hello</pre></div></div></div>
 <div class="section">
-<h3>Adding Plugin Parameters<a name="Adding_Plugin_Parameters"></a></h3>
+<h3><a name="Adding_Plugin_Parameters"></a>Adding Plugin Parameters</h3>
 <p>Now, suppose it's not enough that our plugin display static text to the console. Suppose we need it to display a greeting that is a little more personalized. We can easily add support for this by adding a <b>name</b> parameter. For good measure, we'll output the current project's name as well.</p>
 <div class="section">
-<h4>Change the Ant Script<a name="Change_the_Ant_Script"></a></h4>
+<h4><a name="Change_the_Ant_Script"></a>Change the Ant Script</h4>
 <p>The build script will have to change to output the new information:</p>
 <div class="source">
 <pre>hello.build.xml:
@@ -420,7 +420,7 @@ Dennis Lundberg" />
   &lt;/target&gt;
 &lt;/project&gt;</pre></div></div>
 <div class="section">
-<h4>Change the Mapping Document<a name="Change_the_Mapping_Document"></a></h4>
+<h4><a name="Change_the_Mapping_Document"></a>Change the Mapping Document</h4>
 <p>Now that we have a build script which requires two new parameters, we have to tell the mapping document about them, so they will be injected into the Ant Project instance.</p>
 <div class="source">
 <pre>hello.mojos.xml:
@@ -466,7 +466,7 @@ Dennis Lundberg" />
 <p>The <b>name</b> parameter declaration provides an expression attribute. This allows the user to specify <tt>-Dname=somename</tt> on the command line. Otherwise, the only way to configure this parameter would be through a <tt>&lt;configuration/&gt;</tt> element within the plugin specification in the user's POM. Note that this parameter is required to have a value before our mojo can execute.</p>
 <p>The <b>projectName</b> parameter declaration provides two other interesting items. First, it specifies a <tt>defaultValue</tt> attribute, which specifies an expression to be evaluated against Maven's current build state in order to extract the parameter's value. Second, it specifies a <tt>readonly</tt> attribute, which means the user cannot directly configure this parameter - either via command line or configuration within the POM. It can only be modified by modifying the build state referenced in the <tt>defaultValue</tt>. In our case, the name element of the POM. Also note that this parameter is declared to be required before our mojo can execute.</p></div>
 <div class="section">
-<h4>Rebuild It and Run It<a name="Rebuild_It_and_Run_It"></a></h4>
+<h4><a name="Rebuild_It_and_Run_It"></a>Rebuild It and Run It</h4>
 <p>Now that we've modified our plugin, we have to rebuild it before running it again.</p>
 <div class="source">
 <pre>mvn clean install</pre></div>
@@ -480,13 +480,13 @@ Dennis Lundberg" />
 <div class="source">
 <pre>[echo] Hello, John. You're building project: Hello Plugin</pre></div></div></div>
 <div class="section">
-<h3>Defining Multiple Mojos from One Build Script<a name="Defining_Multiple_Mojos_from_One_Build_Script"></a></h3>
+<h3><a name="Defining_Multiple_Mojos_from_One_Build_Script"></a>Defining Multiple Mojos from One Build Script</h3>
 <p>If you're familiar with Ant, you're probably familiar with the common usage pattern of defining multiple build types within a single build script. For instance, you might have a build type for cleaning the project, another for producing the application JAR file, and yet another for producing the full distribution including Javadocs, etc.</p>
 <p>The concept is pretty simple. Discrete chunks of the build process are separated into targets within the script. These targets can reference one another in order to make reuse within the build script possible.</p>
 <p>These same concepts map pretty well to Maven, actually. However, instead of targets directly referencing one another, they would be bound to the appropriate phases of the build lifecycle. In this way, multiple Ant targets from the same build script can be reused piecemeal at different points in multiple build lifecycles (clean, site, and the main lifecycle are three examples).</p>
 <p>This section will describe how to map multiple logical mojos onto different targets within the same Ant build script. It's also possible to reference targets from multiple build scripts, but we'll cover this later.</p>
 <div class="section">
-<h4>Two Targets, One Script<a name="Two_Targets_One_Script"></a></h4>
+<h4><a name="Two_Targets_One_Script"></a>Two Targets, One Script</h4>
 <p>To test this, we'll split our echo statement into two targets. Then, we'll reference each as separate mojos in the build. The new script looks like this:</p>
 <div class="source">
 <pre>one-two.build.xml:
@@ -502,7 +502,7 @@ Dennis Lundberg" />
   &lt;/target&gt;
 &lt;/project&gt;</pre></div></div>
 <div class="section">
-<h4>Map the Mojos<a name="Map_the_Mojos"></a></h4>
+<h4><a name="Map_the_Mojos"></a>Map the Mojos</h4>
 <p>Next, we'll add new mapping document to map these two new mojos:</p>
 <div class="source">
 <pre>one-two.mojos.xml:
@@ -557,9 +557,9 @@ Dennis Lundberg" />
 &lt;/pluginMetadata&gt;</pre></div>
 <p>Now that we've split the old functionality into two distinct mojos, there are some interesting consequences. Aside from the obvious, mojo <b>one</b> no longer requires a valid project instance in order to execute, since we only require the user's name in order to greet him.</p></div>
 <div class="section">
-<h4>Build It, Run It<a name="Build_It_Run_It"></a></h4></div>
+<h4><a name="Build_It_Run_It"></a>Build It, Run It</h4></div>
 <div class="section">
-<h4>Rebuild It and Run It<a name="Rebuild_It_and_Run_It"></a></h4>
+<h4><a name="Rebuild_It_and_Run_It"></a>Rebuild It and Run It</h4>
 <p>Since we've modified our plugin, we have to rebuild it again before re-running it.</p>
 <div class="source">
 <pre>mvn clean install</pre></div>
@@ -624,13 +624,13 @@ mvn validate</pre></div>
 ...
 [echo] You're building project: Test Project</pre></div></div>
 <div class="section">
-<h4>A Note on Multiple Build Scripts<a name="A_Note_on_Multiple_Build_Scripts"></a></h4>
+<h4><a name="A_Note_on_Multiple_Build_Scripts"></a>A Note on Multiple Build Scripts</h4>
 <p>It's worth mentioning that Ant-driven plugins can just as easily contain multiple Ant build scripts. Simply follow the naming rules - naming each <tt>A.build.xml</tt>, <tt>B.build.xml</tt>, <tt>C.build.xml</tt>, etc. for example - and be sure to provide a mapping document to correspond to each build script that contains a mojo (other build scripts may be contained in the plugin, and referenced by one of these; they don't need mapping documents). So, for the above examples (assuming they all contained mojo targets), you'd need: <tt>A.mojos.xml</tt>, <tt>B.mojos.xml</tt>, and <tt>C.mojos.xml</tt>. If <tt>C.build.xml</tt> was referenced by A and B, but didn't contain mojo targets, then you don't need a <tt>C.mojos.xml</tt> for obvious reasons.</p></div></div>
 <div class="section">
-<h3>Advanced Usage<a name="Advanced_Usage"></a></h3>
+<h3><a name="Advanced_Usage"></a>Advanced Usage</h3>
 <p>Below are some tips on some of the more advanced options related to Ant mojos.</p>
 <div class="section">
-<h4>Component References<a name="Component_References"></a></h4>
+<h4><a name="Component_References"></a>Component References</h4>
 <p>If your plugin needs a reference to a Plexus component, it will have to define something similar to the following in the mapping document:</p>
 <div class="source">
 <pre>&lt;pluginMetadata&gt;
@@ -652,7 +652,7 @@ mvn validate</pre></div>
   &lt;/mojos&gt;
 &lt;/pluginMetadata&gt;</pre></div></div>
 <div class="section">
-<h4>Forking New Lifecycles<a name="Forking_New_Lifecycles"></a></h4>
+<h4><a name="Forking_New_Lifecycles"></a>Forking New Lifecycles</h4>
 <p>In case your plugin needs to fork a new lifecycle, you can include the following in the mapping document:</p>
 <div class="source">
 <pre>&lt;pluginMetadata&gt;
@@ -676,7 +676,7 @@ mvn validate</pre></div>
   &lt;/mojos&gt;
 &lt;/pluginMetadata&gt;</pre></div></div>
 <div class="section">
-<h4>Deprecation<a name="Deprecation"></a></h4>
+<h4><a name="Deprecation"></a>Deprecation</h4>
 <p>As time goes on, you will likely have to deprecate part of your plugin. Whether it's a mojo parameter, or even an entire mojo, Maven can support it, and remind your users that the mojo or configuration they're using is deprecated, and print a message directing them to adjust their usage.</p>
 <p>To deprecate a mojo parameter, simply add this:</p>
 <div class="source">