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 [6/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/docs/3.6.0/release-notes.html
==============================================================================
--- maven/website/content/docs/3.6.0/release-notes.html (original)
+++ maven/website/content/docs/3.6.0/release-notes.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/markdown/docs/3.6.0/release-notes.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/docs/3.6.0/release-notes.md 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">
@@ -150,8 +150,7 @@
<li>the web site: <a class="externalLink" href="https://maven.apache.org/">https://maven.apache.org/</a></li>
<li>the maven-user mailing list: <a href="/mailing-lists.html">https://maven.apache.org/mailing-lists.html</a></li>
<li>the reference documentation: <a href="/ref/3.6.0/">https://maven.apache.org/ref/3.6.0/</a></li>
-</ul>
-<div class="section">
+</ul><section>
<h2><a name="Reporters_and_Contributors_of_this_release"></a>Reporters and Contributors of this release</h2>
<p>We really value the contributions of these non committers, so this section is focused on those individuals. Descriptions of the issues fixed can be found at the <a href="#Details">end of these release notes</a>.</p>
<p>Code Contributors of this release:</p>
@@ -175,8 +174,7 @@
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6490">MNG-6490</a> John Canny</li>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6492">MNG-6492</a> Hoa Phan</li>
</ul>
-<p>Many thanks to all reporters and contributors for their time and support.</p></div>
-<div class="section">
+<p>Many thanks to all reporters and contributors for their time and support.</p></section><section>
<h2><a name="Preliminary_Testers"></a>Preliminary Testers</h2>
<p>Thanks to the following preliminary testers:</p>
<ul>
@@ -186,11 +184,9 @@
<li>Enrico Olivelli</li>
<li>Gary Gregory</li>
<li>Thomas Collignon</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h2><a name="Known_Issues"></a>Known Issues</h2>
-<p>At the time of release, there are no known regressions introduced by this release.</p></div>
-<div class="section">
+<p>At the time of release, there are no known regressions introduced by this release.</p></section><section>
<h2><a name="Overview_about_the_changes"></a>Overview about the changes</h2>
<ul>
@@ -226,7 +222,7 @@
[INFO] ------------------------------------------------------------------------
</pre></div></div>
-<p>The <tt>parent</tt> in the above output is the artifact name of the root module and the <tt>5.0.4-SNAPSHOT</tt> is the versions number for all modules in this reactor build.</p>
+<p>The parent in the above output is the artifact name of the root module and the 5.0.4-SNAPSHOT is the versions number for all modules in this reactor build.</p>
<p>If you have an aggregator pom which contains different modules with different versions each line will contain the appropriate versions which looks like this:</p>
<div>
@@ -250,10 +246,8 @@
<ul>
<li>There was an issue related to the classpath ordering <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6415">MNG-6415</a> in Maven which can cause issues which has been fixed.</li>
-</ul></div>
-<div class="section">
-<h2><a name="The_detailed_issue_list"></a><a href="#Details">The detailed issue list</a></h2>
-<div class="section">
+</ul></section><section>
+<h2><a name="The_detailed_issue_list"></a><a href="#Details">The detailed issue list</a></h2><section>
<h3><a name="Bugs:"></a>Bugs:</h3>
<ul>
@@ -264,8 +258,7 @@
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6415">MNG-6415</a> - Project Artifacts Cache does not retain the order of classpath entries.</li>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6472">MNG-6472</a> - Mockito cannot mock this class: interface org.eclipse.aether.impl.RepositoryEventDispatcher</li>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6490">MNG-6490</a> - Maven shall not fail reporting circular dependency when the dependency is a classified secondary artifact</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Improvements:"></a>Improvements:</h3>
<ul>
@@ -277,14 +270,12 @@
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6467">MNG-6467</a> - Remove plugin definition from pom file which is inherited</li>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6480">MNG-6480</a> - Eclipse.org site is down, and you are unable to build Maven?</li>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6492">MNG-6492</a> - Minor improvement on Array construction, converson</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Task"></a>Task</h3>
<ul>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6475">MNG-6475</a> - Remove guava dependencies</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Dependency_upgrades"></a>Dependency upgrades</h3>
<ul>
@@ -299,10 +290,9 @@
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6496">MNG-6496</a> - Upgrade Maven Resolver to 1.3.1</li>
<li><a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6497">MNG-6497</a> - Upgrade guice to 4.2.1</li>
</ul>
-<p>The full list of changes can be found in our <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12338966">issue management system</a>.</p></div></div>
-<div class="section">
+<p>The full list of changes can be found in our <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12338966">issue management system</a>.</p></section></section><section>
<h2><a name="Complete_Release_Notes"></a>Complete Release Notes</h2>
-<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></div>
+<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></section>
</div>
</div>
</div>
Modified: maven/website/content/docs/3.6.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.6.1/release-notes.html (original)
+++ maven/website/content/docs/3.6.1/release-notes.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/markdown/docs/3.6.1/release-notes.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/docs/3.6.1/release-notes.md 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">
@@ -150,8 +150,7 @@
<li>the web site: <a class="externalLink" href="https://maven.apache.org/">https://maven.apache.org/</a></li>
<li>the maven-user mailing list: <a href="/mailing-lists.html">https://maven.apache.org/mailing-lists.html</a></li>
<li>the reference documentation: <a href="/ref/3.6.1/">https://maven.apache.org/ref/3.6.1/</a></li>
-</ul>
-<div class="section">
+</ul><section>
<h2><a name="Reporters_and_Contributors_of_this_release"></a>Reporters and Contributors of this release</h2>
<p>We really value the contributions of these non committers, so this section is focused on those individuals. Descriptions of the issues fixed can be found at the <a href="#Details">end of these release notes</a>.</p>
<p>Issue Reporters of this release:</p>
@@ -191,8 +190,7 @@
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6533">MNG-6533</a> Michael Istria</li>
</ul>
<p>Many thanks to all reporters and contributors for their time and support.</p>
-<p>(Please send an email to the dev list if we missed one to mention).</p></div>
-<div class="section">
+<p>(Please send an email to the dev list if we missed one to mention).</p></section><section>
<h2><a name="Preliminary_Testers"></a>Preliminary Testers</h2>
<p>Thanks to the following preliminary testers:</p>
<ul>
@@ -200,8 +198,7 @@
<li>Gabriel Belingueres</li>
<li>Francois Papon</li>
<li>Eric Lilja</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h2><a name="Known_Issues"></a>Known Issues</h2>
<p>If you are using Maven reporting, it might happen that you will get an exception which looks like this:</p>
@@ -217,20 +214,19 @@ Caused by: java.lang.NullPointerExceptio
...
</pre></div></div>
-<p>This is caused by using a <tt><reportSet>..</reportSet></tt> which does not contain a <tt><report></report></tt> element.</p>
-<p>Temporarily this issue can circumvented by adding an empty <tt><report></report></tt> element inside the <tt><reportSet></reportSet></tt>.</p>
-<p>An <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6636">issue has been created</a> to track the fix.</p></div>
-<div class="section">
+<p>This is caused by using a <reportSet>..</reportSet> which does not contain a <report></report> element.</p>
+<p>Temporarily this issue can circumvented by adding an empty <report></report> element inside the <reportSet></reportSet>.</p>
+<p>An <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6636">issue has been created</a> to track the fix.</p></section><section>
<h2><a name="Overview_about_the_changes"></a>Overview about the changes</h2>
<ul>
<li>
-<p>An issue has been fixed causing multiple executions of plugin goals, related to using parallel build options like <tt>mvn plugin:goal -T 4</tt>. This resulted in duplicated executions of phases. This has been fixed with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-5965">MNG-5965</a>.</p>
+<p>An issue has been fixed causing multiple executions of plugin goals, related to using parallel build options like mvn plugin:goal -T 4. This resulted in duplicated executions of phases. This has been fixed with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-5965">MNG-5965</a>.</p>
</li>
<li>
-<p>NullPointerException related to call in parallel build like <tt>mvn -T 1C clean javadoc:aggregate</tt> <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-5705">MNG-5705</a></p>
+<p>NullPointerException related to call in parallel build like mvn -T 1C clean javadoc:aggregate <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-5705">MNG-5705</a></p>
</li>
<li>
@@ -238,7 +234,7 @@ Caused by: java.lang.NullPointerExceptio
</li>
<li>
-<p>There had been issues related calling Maven script like this: <tt>mvn -f ..</tt></p>
+<p>There had been issues related calling Maven script like this: mvn -f ..</p>
</li>
<li>Having parentheses within the path, which has been fixed with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6346">MNG-6346</a>.</li>
<li>Script can break having special characters as part of the path, which has been solved with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6256">MNG-6256</a>.</li>
@@ -252,7 +248,7 @@ Caused by: java.lang.NullPointerExceptio
</li>
<li>
-<p>Issue related to support Java 9+ <tt>ClassLoader.findClass(String moduleName, String name)</tt> in Mojos. This has been fixed with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6543">MNG-6543</a>.</p>
+<p>Issue related to support Java 9+ ClassLoader.findClass(String moduleName, String name) in Mojos. This has been fixed with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6543">MNG-6543</a>.</p>
</li>
<li>
@@ -266,8 +262,7 @@ Caused by: java.lang.NullPointerExceptio
<p>Missing export for org.slf4j.event.Level has been done with <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6618">MNG-6618</a></p>
</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h2><a name="User_visible_Changes"></a>User visible Changes</h2>
<p>Maven has now a an option to suppress the transfer progress when downloading/uploading in interactive mode.</p>
@@ -283,7 +278,7 @@ Caused by: java.lang.NullPointerExceptio
<pre class="source">mvn -ntp ... ....
</pre></div></div>
-<p>There had been an issues like <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6505">MNG-6505</a> and <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6059">MNG-6059</a> related to the construction of URL’s etc. within <tt>distributionManagement</tt> and <tt>scm</tt> part in the pom for multi module builds like this:</p>
+<p>There had been an issues like <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6505">MNG-6505</a> and <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6059">MNG-6059</a> related to the construction of URL’s etc. within distributionManagement and scm part in the pom for multi module builds like this:</p>
<div>
<div>
@@ -295,10 +290,8 @@ Caused by: java.lang.NullPointerExceptio
</distributionManagement>
</pre></div></div>
-<p>Detailed explanations can be found in <a class="externalLink" href="https://maven.apache.org/ref/3.6.1/maven-model-builder/index.html#Inheritance_Assembly">Inheritance Assembly</a> and in <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6059">MNG-6059</a></p></div>
-<div class="section">
-<h2><a name="The_detailed_issue_list"></a>The detailed issue list<a href="#Details"></a></h2>
-<div class="section">
+<p>Detailed explanations can be found in <a class="externalLink" href="https://maven.apache.org/ref/3.6.1/maven-model-builder/index.html#Inheritance_Assembly">Inheritance Assembly</a> and in <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6059">MNG-6059</a></p></section><section>
+<h2><a name="The_detailed_issue_list"></a>The detailed issue list<a href="#Details"></a></h2><section>
<h3><a name="Bugs:"></a>Bugs:</h3>
<ul>
@@ -314,16 +307,15 @@ Caused by: java.lang.NullPointerExceptio
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6495">MNG-6495</a> - ModelResolver cannot be null</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6505">MNG-6505</a> - child.(x.y).inherit.append.path value should be inherited</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6506">MNG-6506</a> - Mojos are unable to load package annotations on Java >= 9</li>
-<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6529">MNG-6529</a> - <tt>ProjectBuilder.build(List<File> projects, boolean, ProjectBuildingRequest)</tt> doesn’t honor <tt>ProjectBuildingRequest.isResolveDependencies()</tt></li>
+<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6529">MNG-6529</a> - ProjectBuilder.build(List<File> projects, boolean, ProjectBuildingRequest) doesn’t honor ProjectBuildingRequest.isResolveDependencies()</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6530">MNG-6530</a> - Regression in ProjectBuilder when file change between invocations (introduced by MNG-6311)</li>
-<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6533">MNG-6533</a> - <tt>ProjectBuilder.build(list_of_projects,...)</tt> does not contain MavenProject in exception report</li>
-<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6543">MNG-6543</a> - Upgrade plexus classworld to support java 9+ <tt>ClassLoader.findClass(String moduleName, String name)</tt> in Mojos</li>
+<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6533">MNG-6533</a> - ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in exception report</li>
+<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6543">MNG-6543</a> - Upgrade plexus classworld to support java 9+ ClassLoader.findClass(String moduleName, String name) in Mojos</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6558">MNG-6558</a> - ToolchainsBuildingResult event is not sent on EventSpy</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6577">MNG-6577</a> - pom.xml: Uncaught IllegalArgumentException when parsing unicode entity ref</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6590">MNG-6590</a> - DefaultProjectArtifactsCache java.lang.IllegalStateException: Duplicate artifact resolution result</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6599">MNG-6599</a> - unknown version in model id when version is defined from parent</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Improvements"></a>Improvements</h3>
<ul>
@@ -342,14 +334,12 @@ Caused by: java.lang.NullPointerExceptio
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6601">MNG-6601</a> - add input location tracking for site’s reportPlugins injected by reports conversion</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6605">MNG-6605</a> - Allow to suppress download messages in interactive mode</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6611">MNG-6611</a> - Update animal-sniffer-maven-plugin to 1.17</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Wish"></a>Wish</h3>
<ul>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6571">MNG-6571</a> - Maven memory consumption issue</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Task"></a>Task</h3>
<ul>
@@ -357,18 +347,16 @@ Caused by: java.lang.NullPointerExceptio
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6544">MNG-6544</a> - Replace CacheUtils#{eq,hash} with Objects</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6573">MNG-6573</a> - Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6618">MNG-6618</a> - Maven doesn’t export org.slf4j.event.Level</li>
-</ul></div>
-<div class="section">
+</ul></section><section>
<h3><a name="Dependency_upgrade"></a>Dependency upgrade</h3>
<ul>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6526">MNG-6526</a> - Upgrade to Wagon 3.3.1 (from 3.2.0)</li>
<li><a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-6591">MNG-6591</a> - Upgrade to Wagon 3.3.2</li>
</ul>
-<p>The full list of changes can be found in our <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344378&projectId=12316922">issue management system</a>.</p></div></div>
-<div class="section">
+<p>The full list of changes can be found in our <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344378&projectId=12316922">issue management system</a>.</p></section></section><section>
<h2><a name="Complete_Release_Notes"></a>Complete Release Notes</h2>
-<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></div>
+<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></section>
</div>
</div>
</div>
Modified: maven/website/content/docs/history.html
==============================================================================
--- maven/website/content/docs/history.html (original)
+++ maven/website/content/docs/history.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/markdown/docs/history.md.vm at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/docs/history.md.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">
@@ -141,9 +141,7 @@
-->
<p>Date format is: YYYY-MM-DD</p>
-
-<div class="section">
-<div class="section">
+<section><section>
<h3><a name="Maven_3">Maven 3</a></h3>
<table border="0" class="table table-striped">
@@ -354,8 +352,7 @@
<td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/maven-announce/200911.mbox/%3C4AFD52A3.80707%40apache.org%3E">announce</a>, <a href="./3.0-alpha-3/release-notes.html">release notes</a></td>
</tr>
</table>
-</div>
-<div class="section">
+</section><section>
<h3><a name="Maven_2">Maven 2</a></h3>
<p>Maven 2.x has now reached its <a href="../maven-2.x-eol.html">end of life</a>.
@@ -471,8 +468,7 @@
<td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/maven-users/200510.mbox/%3C4356C7AF.6080901%40apache.org%3E">announce</a>, <a href="./2.0/release-notes.html">release notes</a></td>
</tr>
</table>
-</div>
-<div class="section">
+</section><section>
<h3><a name="Maven_1">Maven 1</a></h3>
<p>Maven 1.x has now reached its <a href="../maven-1.x-eol.html">end of life</a>.
@@ -546,7 +542,7 @@
<td>2002-03-30</td>
<td>1.0-beta-2</td>
<td><a class="externalLink" href="http://jakarta.apache.org/site/news/news-2002.html#0330.1">announce</a></td></tr>
-</table></div></div>
+</table></section></section>
</div>
</div>
</div>
Modified: maven/website/content/download.html
==============================================================================
--- maven/website/content/download.html (original)
+++ maven/website/content/download.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/xdoc/download.xml.vm at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/xdoc/download.xml.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">
@@ -124,7 +124,7 @@
<div id="bodyColumn" class="span10" >
- <div class="section">
+ <section>
<h2><a name="Downloading_Apache_Maven_3.6.1"></a>Downloading Apache Maven 3.6.1</h2>
@@ -173,8 +173,7 @@
</form>
<a name="Requirements"></a>
- <a name="Requirements"></a>
-<div class="section" id="Requirements">
+ <a name="Requirements"></a><section id="Requirements">
<h3><a name="System_Requirements"></a>System Requirements</h3>
<p>
@@ -213,10 +212,9 @@
</tr>
</table>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h3><a name="Files"></a>Files</h3>
<p>Maven is distributed in several formats for your convenience. Simply pick a
@@ -308,10 +306,9 @@
<li>Distributed under the <a class="externalLink" href="https://www.apache.org/licenses/">Apache License, version 2.0</a></li>
</ul>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h3><a name="Previous_Releases"></a>Previous Releases</h3>
<p>It is strongly recommended to use the latest release version of Apache Maven to take advantage of newest features and bug fixes.</p>
@@ -321,8 +318,8 @@
<a href="./docs/history.html">Maven Releases History</a> and can download files from
the <a class="externalLink" href="https://archive.apache.org/dist/maven/maven-3/">archives</a> for versions 3.0.4+
and <a class="externalLink" href="https://archive.apache.org/dist/maven/binaries/">legacy archives</a> for earlier releases.</p>
- </div>
- </div>
+ </section>
+ </section>
</div>
Modified: maven/website/content/errors/404.html
==============================================================================
--- maven/website/content/errors/404.html (original)
+++ maven/website/content/errors/404.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/xdoc/errors/404.xml.vm at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/xdoc/errors/404.xml.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,8 +121,7 @@
<div id="bodyColumn" class="span10" >
-
-<div class="section">
+ <section>
<h2><a name="Page_Not_Found"></a>Page Not Found</h2>
@@ -140,7 +139,7 @@
<p>If you came to this page by following a broken link on our site, you can report the <a class="externalLink" href="https://issues.apache.org/jira/browse/MNGSITE">problem</a>.</p>
- </div>
+ </section>
</div>
Modified: maven/website/content/examples/index.html
==============================================================================
--- maven/website/content/examples/index.html (original)
+++ maven/website/content/examples/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/examples/index.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/examples/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">
@@ -120,11 +120,11 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Examples"></a>Examples</h2>
<ul>
<li><a href="./injecting-properties-via-settings.html">Injecting POM Properties via settings.xml</a></li>
-<li><a href="./maven-3-lifecycle-extensions.html">Maven 3 lifecycle extensions</a></li></ul></div>
+<li><a href="./maven-3-lifecycle-extensions.html">Maven 3 lifecycle extensions</a></li></ul></section>
</div>
</div>
</div>
Modified: maven/website/content/examples/injecting-properties-via-settings.html
==============================================================================
--- maven/website/content/examples/injecting-properties-via-settings.html (original)
+++ maven/website/content/examples/injecting-properties-via-settings.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/examples/injecting-properties-via-settings.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/examples/injecting-properties-via-settings.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,12 +120,10 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Example:_Injecting_POM_Properties_via_Settings.xml"></a>Example: Injecting POM Properties via Settings.xml</h2>
-<div class="section">
+<section>
+<h2><a name="Example:_Injecting_POM_Properties_via_Settings.xml"></a>Example: Injecting POM Properties via Settings.xml</h2><section>
<h3><a name="Impetus"></a>Impetus</h3>
-<p>You have a plugin parameter that should contain a user-specific value. This parameter has a common format (relative directory structure), but depends on knowing the directory of the installed application or something.</p></div>
-<div class="section">
+<p>You have a plugin parameter that should contain a user-specific value. This parameter has a common format (relative directory structure), but depends on knowing the directory of the installed application or something.</p></section><section>
<h3><a name="Plugin_Configuration"></a>Plugin Configuration</h3>
<div class="source"><pre class="prettyprint linenums"><project>
[...]
@@ -140,9 +138,8 @@
</configuration>
</plugin>
</plugins>
- </build></pre></div></div>
-<div class="section">
-<h3><a name="settings.xml"></a><tt>settings.xml</tt></h3>
+ </build></pre></div></section><section>
+<h3><a name="settings.xml"></a><code>settings.xml</code></h3>
<div class="source"><pre class="prettyprint linenums"><settings>
[...]
<profiles>
@@ -157,10 +154,9 @@
<activeProfiles>
<activeProfile>inject-application-home</activeProfile>
</activeProfiles>
-</settings></pre></div></div>
-<div class="section">
+</settings></pre></div></section><section>
<h3><a name="Explanation"></a>Explanation</h3>
-<p>When Maven loads the project's POM, it will pickup the activated profiles from the <tt>activeProfiles</tt> section of the <tt>settings.xml</tt> file, and inject the properties declared within the profile. When the POM is interpolated, the <tt>application-home</tt> property will already have been injected, so will allow the plugin's parameter value to be resolved.</p></div></div>
+<p>When Maven loads the project's POM, it will pickup the activated profiles from the <code>activeProfiles</code> section of the <code>settings.xml</code> file, and inject the properties declared within the profile. When the POM is interpolated, the <code>application-home</code> property will already have been injected, so will allow the plugin's parameter value to be resolved.</p></section></section>
</div>
</div>
</div>
Modified: maven/website/content/examples/maven-3-lifecycle-extensions.html
==============================================================================
--- maven/website/content/examples/maven-3-lifecycle-extensions.html (original)
+++ maven/website/content/examples/maven-3-lifecycle-extensions.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/examples/maven-3-lifecycle-extensions.apt.vm at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/examples/maven-3-lifecycle-extensions.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">
@@ -132,18 +132,16 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Example:_Using_Maven_3_lifecycle_extension"></a>Example: Using Maven 3 lifecycle extension</h2>
-<div class="section">
+<section>
+<h2><a name="Example:_Using_Maven_3_lifecycle_extension"></a>Example: Using Maven 3 lifecycle extension</h2><section>
<h3><a name="Lifecyle_Participation"></a>Lifecyle Participation</h3>
<p>You can extend multiple classes depending on your needs:</p>
<ul>
-<li><a href="/ref/current/maven-core/apidocs/index.html?org/apache/maven/execution/AbstractExecutionListener.html"><tt>org.apache.maven.execution.AbstractExecutionListener</tt></a>,</li>
-<li><a href="/ref/current/maven-core/apidocs/index.html?org/apache/maven/AbstractMavenLifecycleParticipant.html"><tt>org.apache.maven.AbstractMavenLifecycleParticipant</tt></a>,</li>
-<li><a href="/ref/current/maven-core/apidocs/index.html?org/apache/maven/eventspy/AbstractEventSpy.html"><tt>org.apache.maven.eventspy.AbstractEventSpy</tt></a>,</li></ul></div>
-<div class="section">
+<li><a href="/ref/current/maven-core/apidocs/index.html?org/apache/maven/execution/AbstractExecutionListener.html"><code>org.apache.maven.execution.AbstractExecutionListener</code></a>,</li>
+<li><a href="/ref/current/maven-core/apidocs/index.html?org/apache/maven/AbstractMavenLifecycleParticipant.html"><code>org.apache.maven.AbstractMavenLifecycleParticipant</code></a>,</li>
+<li><a href="/ref/current/maven-core/apidocs/index.html?org/apache/maven/eventspy/AbstractEventSpy.html"><code>org.apache.maven.eventspy.AbstractEventSpy</code></a>,</li></ul></section><section>
<h3><a name="Build_your_extension"></a>Build your extension</h3>
-<p>Create a Maven project with a dependency on <tt>org.apache.maven:maven-core:3.6.1</tt> and other dependencies:</p>
+<p>Create a Maven project with a dependency on <code>org.apache.maven:maven-core:3.6.1</code> and other dependencies:</p>
<div class="source"><pre class="prettyprint linenums"> <groupId>org.apache.maven.extensions</groupId>
<artifactId>beer-maven-lifecycle</artifactId>
<version>1.0-SNAPSHOT</version>
@@ -202,15 +200,14 @@ public class BeerMavenLifecycleParticipa
...
</plugins>
...
- </build></pre></div></div>
-<div class="section">
+ </build></pre></div></section><section>
<h3><a name="Use_your_extension_in_your_build.28s.29"></a>Use your extension in your build(s)</h3>
<p>You have 3 ways to use your extension within your builds:</p>
<ul>
-<li>add your extension jar in <tt>${maven.home}/lib/ext</tt>,</li>
+<li>add your extension jar in <code>${maven.home}/lib/ext</code>,</li>
<li>add it as a build extension in your pom,</li>
-<li>(since Maven 3.3.1) configure your extension in <a href="/ref/current/maven-embedder/core-extensions.html"><tt>.mvn/extensions.xml</tt></a>.</li></ul>
-<p><b>NOTE</b>: if you use the build extension mechanism, the method <tt>afterSessionStart</tt> <b>won't be called</b> since the extension is loaded later in the build</p>
+<li>(since Maven 3.3.1) configure your extension in <a href="/ref/current/maven-embedder/core-extensions.html"><code>.mvn/extensions.xml</code></a>.</li></ul>
+<p><b>NOTE</b>: if you use the build extension mechanism, the method <code>afterSessionStart</code> <b>won't be called</b> since the extension is loaded later in the build</p>
<p>To use a build extension in your project, declare it in your pom as:</p>
<div class="source"><pre class="prettyprint linenums"> <build>
...
@@ -224,7 +221,7 @@ public class BeerMavenLifecycleParticipa
...
</extensions>
...
- </build></pre></div></div></div>
+ </build></pre></div></section></section>
</div>
</div>
</div>
Modified: maven/website/content/general.html
==============================================================================
--- maven/website/content/general.html (original)
+++ maven/website/content/general.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/fml/general.fml at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/fml/general.fml 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">
@@ -133,7 +133,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Frequently_Asked_Technical_Questions"></a><a name="top">Frequently Asked Technical Questions</a></h2>
<ol style="list-style-type: decimal">
<li><a href="#encoding-warning">How do I prevent "[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!"</a></li>
@@ -158,7 +158,7 @@
<li><a href="#How_to_produce_execution_debug_output_or_error_messages">How to produce execution debug output or error messages?</a></li>
<li><a href="#What_is_a_Mojo">What is a Mojo?</a></li>
<li><a href="#How_to_find_dependencies">How to find dependencies on public Maven repositories?</a></li>
-<li><a href="#javadoc_jar_built_twice">Why is my Javadoc JAR built twice during release?</a></li></ol></div>
+<li><a href="#javadoc_jar_built_twice">Why is my Javadoc JAR built twice during release?</a></li></ol></section>
<dl>
<dt><a name="encoding-warning">How do I prevent "[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!"</a></dt>
<dd>
@@ -184,7 +184,7 @@
<p>
The scope you should use for this is
- <tt>provided</tt>. This indicates to Maven that the dependency will be
+ <code>provided</code>. This indicates to Maven that the dependency will be
provided at run time by its container or the JDK, for example.
</p>
@@ -208,7 +208,7 @@
<p>
You can use the <a href="/plugins/maven-help-plugin/">Maven Help Plugin</a>'s
- <a href="/plugins/maven-help-plugin/describe-mojo.html"><tt>describe</tt></a> goal.
+ <a href="/plugins/maven-help-plugin/describe-mojo.html"><code>describe</code></a> goal.
For example, to find out the version of the install plugin:
</p>
@@ -302,8 +302,8 @@
</p>
<p>
- By configuring <tt><sourceDirectory></tt>, <tt><resources></tt> and other elements of
- the <tt><build></tt> section.
+ By configuring <code><sourceDirectory></code>, <code><resources></code> and other elements of
+ the <code><build></code> section.
</p>
<p>
@@ -380,8 +380,8 @@ Where: <path-to-file> the path to
<p>
- So, if you have subscribed to <tt>users@maven.apache.org</tt> then you would
- send a message to <tt>users-unsubscribe@maven.apache.org</tt> in order to
+ So, if you have subscribed to <code>users@maven.apache.org</code> then you would
+ send a message to <code>users-unsubscribe@maven.apache.org</code> in order to
get off the list.
People tend to have problems when they subscribe with one address and
attempt to unsubscribe with another. So make sure that you are using the
@@ -391,7 +391,7 @@ Where: <path-to-file> the path to
<p>
If you find you still cannot get off a list then
- send a message to <tt>[mailing-list]-help@maven.apache.org</tt>. These
+ send a message to <code>[mailing-list]-help@maven.apache.org</code>. These
instructions are also appended to every message sent out on a maven mailing
list ...
</p>
@@ -399,7 +399,7 @@ Where: <path-to-file> the path to
<p align="right"><a href="#top">[top]</a></p><hr /></dd>
<dt><a name="skip-test">How do I skip the tests?</a></dt>
<dd>
- Add the parameter <tt>-Dmaven.test.skip=true</tt> or <tt>-DskipTests=true</tt> in the command line,
+ Add the parameter <code>-Dmaven.test.skip=true</code> or <code>-DskipTests=true</code> in the command line,
depending on whether you want to skip test compilation and execution or only execution. See the example
<a href="/plugins/maven-surefire-plugin/examples/skipping-tests.html">Skipping Tests</a>
in <a href="/plugins/maven-surefire-plugin/">the Surefire Plugin's documentation</a> for more details.
@@ -407,7 +407,7 @@ Where: <path-to-file> the path to
<p align="right"><a href="#top">[top]</a></p><hr /></dd>
<dt><a name="run-one-test">How can I run a single unit test?</a></dt>
<dd>
- Use the parameter <tt>-Dtest=MyTest</tt> at the command line.
+ Use the parameter <code>-Dtest=MyTest</code> at the command line.
NB: do not specify the entire package (org.apache.x.y.MyTest)
<p align="right"><a href="#top">[top]</a></p><hr /></dd>
@@ -415,7 +415,7 @@ Where: <path-to-file> the path to
<dd>
<p>Configure your ide to use the correct encoding. With Eclipse, add
- <tt>-Dfile.encoding=ISO-8859-1</tt> in eclipse.ini file</p>
+ <code>-Dfile.encoding=ISO-8859-1</code> in eclipse.ini file</p>
<p>Configure the reporting output encoding in your pom
</p>
@@ -445,7 +445,7 @@ Where: <path-to-file> the path to
<p>
Configure the file encoding use by mvn.
add to MAVEN_OPTS the encoding (same as the ide).
- This can be made with adding <tt>MAVEN_OPTS="-Dfile.encoding=ISO-8859-1"</tt> in <tt>$HOME/.profile</tt>
+ This can be made with adding <code>MAVEN_OPTS="-Dfile.encoding=ISO-8859-1"</code> in <code>$HOME/.profile</code>
</p>
<p align="right"><a href="#top">[top]</a></p><hr /></dd>
@@ -579,8 +579,8 @@ Where: <path-to-file> the path to
<p align="right"><a href="#top">[top]</a></p><hr /></dd>
<dt><a name="javadoc_jar_built_twice">Why is my Javadoc JAR built twice during release?</a></dt>
<dd>
- With MNG-5940 the release profile goal of the Maven Javadoc Plugin has been changed to <tt>
- jar-no-fork</tt>. Revise your configuration to avoid duplicate JAR upload.
+ With MNG-5940 the release profile goal of the Maven Javadoc Plugin has been changed to <code>
+ jar-no-fork</code>. Revise your configuration to avoid duplicate JAR upload.
<p align="right"><a href="#top">[top]</a></p></dd></dl>
</div>
Modified: maven/website/content/glossary.html
==============================================================================
--- maven/website/content/glossary.html (original)
+++ maven/website/content/glossary.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/markdown/glossary.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/glossary.md 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">
@@ -118,7 +118,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Glossary"></a>Glossary</h2>
<p>This document describes some of the most common terms encountered while using Maven. These terms, that have an explicit meaning for Maven, can sometimes be confusing for newcomers.</p>
<ul>
@@ -137,7 +137,7 @@
</li>
<li>
-<p><b>GroupId</b>: A group ID is a universally unique identifier for a project. While this is often just the project name (eg. <tt>commons-collections</tt>), it is helpful to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. <tt>org.apache.maven</tt>).</p>
+<p><b>GroupId</b>: A group ID is a universally unique identifier for a project. While this is often just the project name (eg. commons-collections), it is helpful to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. org.apache.maven).</p>
</li>
<li>
@@ -158,8 +158,8 @@
</li>
<li>
-<p><b>Snapshots</b>: Projects can (and should) have a special version including <tt>SNAPSHOT</tt> to indicate that they are a “work in progress”, and are not yet released. When a snapshot dependency is encountered, it is always looked for in all remote repositories, and downloaded again if newer than the local copy.</p>
-<p>The version can either be the string <tt>SNAPSHOT</tt> itself, indicating “the very latest” development version, or something like <tt>1.1-SNAPSHOT</tt>, indicating development that will be released as 1.1 (i.e. newer than 1.0, but not yet 1.1).</p>
+<p><b>Snapshots</b>: Projects can (and should) have a special version including SNAPSHOT to indicate that they are a “work in progress”, and are not yet released. When a snapshot dependency is encountered, it is always looked for in all remote repositories, and downloaded again if newer than the local copy.</p>
+<p>The version can either be the string SNAPSHOT itself, indicating “the very latest” development version, or something like 1.1-SNAPSHOT, indicating development that will be released as 1.1 (i.e. newer than 1.0, but not yet 1.1).</p>
</li>
<li>
@@ -171,7 +171,7 @@
<p><b>XDoc</b>: XDoc is the format of documentation that Maven currently understands. It is quite simple, and allows embedding XHTML within a simple layout that is transformed into a uniform site.</p>
<p>For information on how to create XDoc files, refer to the <a href="./guides/mini/guide-site.html">Guide to creating a site</a> document.</p>
</li>
-</ul></div>
+</ul></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/development/guide-building-maven.html
==============================================================================
--- maven/website/content/guides/development/guide-building-maven.html (original)
+++ maven/website/content/guides/development/guide-building-maven.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/development/guide-building-maven.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/development/guide-building-maven.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,40 +135,33 @@ Jason van Zyl" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Building_Maven"></a>Building Maven</h2>
-<div class="section">
+<section>
+<h2><a name="Building_Maven"></a>Building Maven</h2><section>
<h3><a name="Why_would_I_want_to_build_Maven.3F"></a>Why would I want to build Maven?</h3>
<p>Building Maven yourself is for one of two reasons:</p>
<ul>
<li>to try out a bleeding edge feature or bugfix (issues can be found in <a href="/issue-management.html"> JIRA</a>),</li>
-<li>to fix a problem you are having and submit a patch to the developers team.</li></ul></div>
-<div class="section">
+<li>to fix a problem you are having and submit a patch to the developers team.</li></ul></section><section>
<h3><a name="Checking_out_the_sources"></a>Checking out the sources</h3>
-<p>All of the source code for Maven and its related libraries is in managed in the ASF source code repositories: for details, see <a href="/scm.html">https://maven.apache.org/scm.html</a>.</p></div>
-<div class="section">
-<h3><a name="Building_Maven"></a>Building Maven</h3>
-<div class="section">
+<p>All of the source code for Maven and its related libraries is in managed in the ASF source code repositories: for details, see <a href="/scm.html">https://maven.apache.org/scm.html</a>.</p></section><section>
+<h3><a name="Building_Maven"></a>Building Maven</h3><section>
<h4><a name="Building_a_Maven_Plugin_or_Component"></a>Building a Maven Plugin or Component</h4>
<p>Building a Maven plugin or component is like any Maven build:</p>
-<div class="source"><pre class="prettyprint linenums">mvn install</pre></div>
-<div class="section">
+<div class="source"><pre class="prettyprint linenums">mvn install</pre></div><section>
<h5><a name="Running_Integration_Tests"></a>Running Integration Tests</h5>
-<p>Before submitting a patch, it is advised to run the integration tests, which are available in the <tt>run-its</tt> profile:</p>
-<div class="source"><pre class="prettyprint linenums">mvn -Prun-its install</pre></div></div></div>
-<div class="section">
+<p>Before submitting a patch, it is advised to run the integration tests, which are available in the <code>run-its</code> profile:</p>
+<div class="source"><pre class="prettyprint linenums">mvn -Prun-its install</pre></div></section></section><section>
<h4><a name="Building_Maven_core"></a>Building Maven core</h4>
<p>Until Maven 3.3, Maven core build could be boostrapped with an Ant build. This bootstrap has been removed in Maven 3.5: you need a pre-built Maven to build Maven from source.</p>
<p>To do this, run from the source directory:</p>
<div class="source"><pre class="prettyprint linenums">mvn install</pre></div>
-<p>The assemblies will be created in <tt>apache-maven</tt>, and can be manually unzipped to the location where you'd like the resulting Maven installed.</p>
-<p>If you want to have the resulting Maven directly copied to a directory, you can use the <tt>distributionTargetDir</tt> property:</p>
-<div class="source"><pre class="prettyprint linenums">mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-SNAPSHOT" install</pre></div>
-<div class="section">
+<p>The assemblies will be created in <code>apache-maven</code>, and can be manually unzipped to the location where you'd like the resulting Maven installed.</p>
+<p>If you want to have the resulting Maven directly copied to a directory, you can use the <code>distributionTargetDir</code> property:</p>
+<div class="source"><pre class="prettyprint linenums">mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-SNAPSHOT" install</pre></div><section>
<h5><a name="Running_the_full_Maven_core_integration_tests"></a>Running the full Maven core integration tests</h5>
-<p>Before checking in a change or submitting a patch to Maven core, it is required to run the core integration tests. These live in their own <a href="/core-its/source-repository.html"><tt>maven-integration-testing.git</tt> Git repository</a>. Using your local build of Maven, run:</p>
+<p>Before checking in a change or submitting a patch to Maven core, it is required to run the core integration tests. These live in their own <a href="/core-its/source-repository.html"><code>maven-integration-testing.git</code> Git repository</a>. Using your local build of Maven, run:</p>
<div class="source"><pre class="prettyprint linenums">mvn test -Prun-its</pre></div>
-<p>Consult <a href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more options.</p></div></div></div></div>
+<p>Consult <a href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more options.</p></section></section></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/development/guide-committer-school.html
==============================================================================
--- maven/website/content/guides/development/guide-committer-school.html (original)
+++ maven/website/content/guides/development/guide-committer-school.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/development/guide-committer-school.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/development/guide-committer-school.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">
@@ -121,14 +121,13 @@ Robert Scholte" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Do_you_want_to_become_a_Maven_Committer.3F"></a>Do you want to become a Maven Committer?</h2>
<p>The Apache Software Foundation is a meritocracy. By this we mean that you gain status based on the merit of your work and actions. In fact the status that you gain is a recognition of the merit of your work and actions.</p>
<p>Maven is an Apache project, that means that we have to follow the Apache rules and way. One of those rules is that we cannot hand out commit access to anyone who asks for it.</p>
<p>To gain commit access you must establish your merit by submitting patches that get picked up by existing committers.</p>
<p>After you have contributed enough patches to establish merit, the project management committee decides whether you can be trusted with commit access.</p>
-<p><i>The reality is that "It is what it is"TL;DR To become a Maven committer write good patches and get them applied.</i></p></div>
-<div class="section">
+<p><i>The reality is that "It is what it is"TL;DR To become a Maven committer write good patches and get them applied.</i></p></section><section>
<h2><a name="What_makes_a_good_patch.3F"></a>What makes a good patch?</h2>
<p>A good patch is a patch that applies cleanly and includes tests that cover both the positive and negative case and has documentation where relevant.</p>
<p>For example, if you were implementing a patch to fix <a class="externalLink" href="http://issues.apache.org/jira/browse/MNG-4612">MNG-4612</a> you would first need to write a test case that is failing when trying to encrypt</p>
@@ -147,21 +146,19 @@ Robert Scholte" />
<li>I revert the src/main and run the tests. If the tests all pass, then there are no test cases to catch the bug => <b>Patch is no good, ask on JIRA for proper tests</b></li>
<li>I revert src and run the tests. If any tests fail, then there is something wrong with the existing code => <b>If I have time I might try and fix the issue, otherwise I just move on</b></li>
<li>I apply the patch a second time and run the tests. If the tests all pass => <b>Patch is good, I commit the patch and mark the JIRA as resolved</b></li></ol>
-<p>So there you have it, my guide to writing good patches... now the next step is getting your patches noticed...</p></div>
-<div class="section">
+<p>So there you have it, my guide to writing good patches... now the next step is getting your patches noticed...</p></section><section>
<h2><a name="How_to_get_your_patches_noticed"></a>How to get your patches noticed</h2>
<p>The simplest way to get your patches noticed is to submit them to the JIRA issue that they fix.</p>
<p>Remember that the Maven project is run by volunteers in their spare time, so very often we may not notice your patch for a few days. </p>
<p>If you are certain that your patch is a good patch, and a week has passed with no comments on JIRA, then you should send <i>one and only one</i> email to the <a class="externalLink" href="mailto:dev@maven.apache.org">dev@maven.apache.org</a> mailing list to see if your patch can get noticed.</p>
-<p><b>Note:</b> you need to be fairly confident that your patch is a good patch, because if you keep on pestering the Maven developers looking to have non-good patches applied, your merit will become negative and people will be less inclined to help you get your patches applied... also this is why you should send one and <i>only one</i> email about your patch on any specific JIRA issue.</p></div>
-<div class="section">
+<p><b>Note:</b> you need to be fairly confident that your patch is a good patch, because if you keep on pestering the Maven developers looking to have non-good patches applied, your merit will become negative and people will be less inclined to help you get your patches applied... also this is why you should send one and <i>only one</i> email about your patch on any specific JIRA issue.</p></section><section>
<h2><a name="Stephen.2C_Arnaud_.26_Barrie.27s_school_for_potential_Maven_committers"></a>Stephen, Arnaud & Barrie's school for potential Maven committers</h2>
<p>To help people who are interested in becoming Maven committers fulfill their goals, myself, Arnaud Heritier and Barrie Treloar (along with any other current Maven committers who decide to help) will be running an assignment based class to help people become committers. </p>
<p>To register for the class you need to complete the following steps:</p>
<ol style="list-style-type: decimal">
<li>Read the <a class="externalLink" href="http://www.apache.org/licenses/icla.txt">Apache Individual Contributor License Agreement</a>. When you graduate from the class you will be required to sign this in order to become a committer.</li>
<li>Subscribe to the <a class="externalLink" href="mailto:dev@maven.apache.org">dev@maven.apache.org</a> mailing list.</li>
-<li>Send an email to the list with the Subject line: <tt>[Committer School] I would like to become a committer</tt> and the Message body:
+<li>Send an email to the list with the Subject line: <code>[Committer School] I would like to become a committer</code> and the Message body:
<div>
<pre>I am interested in the following areas:
_______, _______ and ______
@@ -170,7 +167,7 @@ If anyone knows any issues that I could
Thanks</pre></div></li></ol>
<p>Once you have registered your class assignments are basically to find JIRA issues that you want to fix. The issues can be in any part of Maven, but it is best to start with the areas you have the most interest in. Once you have found a JIRA issue that you are interested in fixing, the process will work a little something like this:</p>
<ol style="list-style-type: decimal">
-<li>Make sure that nobody else is working on the issue and that the issue is one that should be fixed by sending an email to the list with a Subject line something like: <tt>[Committer School] Should I fix MNG-4612?</tt> The Message body should be something like:
+<li>Make sure that nobody else is working on the issue and that the issue is one that should be fixed by sending an email to the list with a Subject line something like: <code>[Committer School] Should I fix MNG-4612?</code> The Message body should be something like:
<div>
<pre>I have had a look at MNG-4612 and I think this is a real issue because...
@@ -180,7 +177,7 @@ Is that the correct way to go about fixi
Thanks</pre></div></li>
<li>Wait a couple of days. Arnaud, Barrie and I will do our best to respond quickly to all such emails, but please keep in mind that we are doing this in our spare time.</li>
-<li>If you get the all clear, develop your patch and upload it to the JIRA, after it is uploaded, send an email to the list with a subject line something like: <tt>[Committer School] Patch for review: MNG-4612</tt> The Message body should be something like:
+<li>If you get the all clear, develop your patch and upload it to the JIRA, after it is uploaded, send an email to the list with a subject line something like: <code>[Committer School] Patch for review: MNG-4612</code> The Message body should be something like:
<div>
<pre>I have tested that this is a good patch and I would appreciate if a committer could review and apply
@@ -188,7 +185,7 @@ Thanks</pre></div></li></ol>
<p>Keep in mind that the Committer School is just a way for us to identify people who are committed to developing patches with a view to eventually becoming committers. </p>
<p>When we have enough evidence that we think we can get you accepted as a committer we will nominate you and hopefully your nomination will be accepted.</p>
<p>Personally, if I see somebody averaging a good patch a week for 2-3 months and being active helping out on the <a class="externalLink" href="mailto:users@maven.apache.org">users@maven.apache.org</a> and <a class="externalLink" href="mailto:dev@maven.apache.org">dev@maven.apache.org</a> mailing lists then I think I could make a strong case for such a person being given commit access.</p>
-<p>So if you think you have the right stuff and want to become a Maven committer... class enrollment is open!</p></div>
+<p>So if you think you have the right stuff and want to become a Maven committer... class enrollment is open!</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/development/guide-documentation-style.html
==============================================================================
--- maven/website/content/guides/development/guide-documentation-style.html (original)
+++ maven/website/content/guides/development/guide-documentation-style.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/development/guide-documentation-style.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/development/guide-documentation-style.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,13 +120,11 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Guide_To_Maven_Documentation_Style"></a>Guide To Maven Documentation Style</h2>
-<div class="section">
+<section>
+<h2><a name="Guide_To_Maven_Documentation_Style"></a>Guide To Maven Documentation Style</h2><section>
<h3><a name="Where_did_the_style_came_from.3F"></a>Where did the style came from?</h3>
<p>The documentation style guide was created to make our documentation more consistent and also to apply best practices to the documentation as well. The standard has just been started and will expand over time based on the suggestions made on the Maven dev mailing list. It is a community consensus of how we should write our documentation.</p>
-<p>Each rule in this guide should come with a motivation as to why it exists. References to external sources are encouraged.</p></div>
-<div class="section">
+<p>Each rule in this guide should come with a motivation as to why it exists. References to external sources are encouraged.</p></section><section>
<h3><a name="Date_format"></a>Date format</h3>
<p>How people format a date varies around the world, sometimes making it hard for people to understand each other. The solution to this problem comes in the form of the ISO-8601 standard.</p>
<p>A date in our documentation must follow this standard:</p>
@@ -139,19 +137,16 @@
Dennis Lundberg
------
2008-07-03
- ------</pre></div>
-<div class="section">
+ ------</pre></div><section>
<h4><a name="References"></a>References</h4>
<ul>
<li><a class="externalLink" href="http://www.w3.org/QA/Tips/iso-date">W3C Quality Web Tips</a></li>
<li><a class="externalLink" href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=26780">ISO-8601</a></li>
-<li><a class="externalLink" href="http://en.wikipedia.org/wiki/ISO_8601">Wikipedia</a></li></ul></div></div>
-<div class="section">
+<li><a class="externalLink" href="http://en.wikipedia.org/wiki/ISO_8601">Wikipedia</a></li></ul></section></section><section>
<h3><a name="POM_Snippet"></a>POM Snippet</h3>
<p>A POM file must use 2 spaces for each indentation. Because POM snippets are often used in documentation to show the user how to configure something, it is important that these snippets aren't too wide. If the are too wide it will make the page difficult to read on a smaller screen.</p>
<p>When you use a snippet of XML from the POM as an example in your documentation, you need to make sure that the example is properly indented. A user should be able to copy and paste the example into their own POM without the need to change the indentation afterwards.</p>
-<p>Also, you should declare all parent POM elements to improve the comprehension. You could use ellipsis (i.e. ...) if you don't want to specify elements.</p>
-<div class="section">
+<p>Also, you should declare all parent POM elements to improve the comprehension. You could use ellipsis (i.e. ...) if you don't want to specify elements.</p><section>
<h4><a name="Example"></a>Example</h4>
<p>The following is an example of how the distribution management of the Maven site is configured.</p>
<div class="source"><pre class="prettyprint linenums"><project>
@@ -164,20 +159,17 @@
</distributionManagement>
...
</project></pre></div>
-<p>As you can see above the <tt><distributionManagement></tt> element is indented once (=2 spaces), the <tt><site></tt> element in indented twice (=4 spaces) and the <tt><id></tt> is indented three times (=6 spaces).</p></div></div>
-<div class="section">
+<p>As you can see above the <code><distributionManagement></code> element is indented once (=2 spaces), the <code><site></code> element in indented twice (=4 spaces) and the <code><id></code> is indented three times (=6 spaces).</p></section></section><section>
<h3><a name="Naming_Documentation_Files"></a>Naming Documentation Files</h3>
<p>All file names should replace space by a minus (-), for instance for this given APT document:</p>
-<div class="source"><pre class="prettyprint linenums"> guide-documentation-style.apt</pre></div></div>
-<div class="section">
+<div class="source"><pre class="prettyprint linenums"> guide-documentation-style.apt</pre></div></section><section>
<h3><a name="Updating_Documentation_Files"></a>Updating Documentation Files</h3>
-<p>A good practice is to update the date (with the correct date format) when you are updating documentation files.</p></div>
-<div class="section">
+<p>A good practice is to update the date (with the correct date format) when you are updating documentation files.</p></section><section>
<h3><a name="Write_Thinking"></a>Write Thinking</h3>
<p>Here are some pointers about English rules when typing material:</p>
<ul>
<li><a class="externalLink" href="http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style">Wikipedia:Manual of Style</a>, specifically <a class="externalLink" href="http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Punctuation">Punctuation Part</a></li>
-<li><a class="externalLink" href="http://developer.gnome.org/projects/gtp/style-guides/pdf/styleguide-C.pdf">Linguistic Style Guidelines</a>, specifically the "Grammatical Guidelines" chapter.</li></ul></div></div>
+<li><a class="externalLink" href="http://developer.gnome.org/projects/gtp/style-guides/pdf/styleguide-C.pdf">Linguistic Style Guidelines</a>, specifically the "Grammatical Guidelines" chapter.</li></ul></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/development/guide-helping.html
==============================================================================
--- maven/website/content/guides/development/guide-helping.html (original)
+++ maven/website/content/guides/development/guide-helping.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/development/guide-helping.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/development/guide-helping.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">
@@ -131,7 +131,7 @@ Jason van Zyl" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_to_helping_with_Maven"></a>Guide to helping with Maven</h2>
<p>As with any open source project, there are several ways you can help:</p>
<ul>
@@ -142,28 +142,24 @@ Jason van Zyl" />
<li><a href="./guide-testing-releases.html"> test releases</a> help test releases that are being voted on (see the dev@maven.apache.org <a href="../../mailing-lists.html"> mailing list</a> for release votes)</li>
<li><a href="./guide-testing-development-plugins.html"> test snapshot plugins</a> help test the latest development versions of plugins and report issues</li>
<li>Help with the documentation by pointing out areas that are lacking or unclear, and if you can, submitting Pull Requests to correct it: use the "edit" button in the breadcrumb, just after the page title. You can also create appropriate issues <a class="externalLink" href="https://issues.apache.org/jira/browse/MNGSITE">by using the issue management system</a>.</li></ul>
-<p>Your participation in the community is much appreciated!</p></div>
-<div class="section">
+<p>Your participation in the community is much appreciated!</p></section><section>
<h2><a name="Why_Would_I_Want_to_Help.3F"></a>Why Would I Want to Help?</h2>
<p>There are several reasons these are good things.</p>
<ul>
<li>By answering other people's questions, you can learn more for yourself</li>
<li>By submitting your own fixes, they get incorporated faster</li>
<li>By reporting issues, you ensure that bugs don't get missed, or forgotten</li>
-<li>You are giving back to a community that has given you software for free</li></ul></div>
-<div class="section">
+<li>You are giving back to a community that has given you software for free</li></ul></section><section>
<h2><a name="How_do_I_Join_the_Project.3F"></a>How do I Join the Project?</h2>
<p>Projects at Apache operate under a meritocracy, meaning those that the developers notice participating to a high extent will be invited to join the project as a committer.</p>
-<p>This is as much based on personality and ability to work with other developers and the community as it is with proven technical ability. Being unhelpful to other users, or obviously looking to become a committer for bragging rights and nothing else is frowned upon, as is asking to be made a committer without having contributed sufficiently to be invited.</p></div>
-<div class="section">
+<p>This is as much based on personality and ability to work with other developers and the community as it is with proven technical ability. Being unhelpful to other users, or obviously looking to become a committer for bragging rights and nothing else is frowned upon, as is asking to be made a committer without having contributed sufficiently to be invited.</p></section><section>
<h2><a name="Developers_Conventions"></a>Developers Conventions</h2>
<p>There are a number of conventions used in the project, which contributors and developers alike should follow for consistency's sake.</p>
<ul>
<li><a href="../../developers/conventions/code.html">Maven Code Style And Convention</a></li>
<li><a href="../../developers/conventions/jira.html">Maven Jira Convention</a></li>
<li><a href="../../developers/conventions/git.html">Maven Git Convention</a></li>
-<li><a href="../../developers/release/index.html">Releasing a Maven project</a></li></ul></div>
-<div class="section">
+<li><a href="../../developers/release/index.html">Releasing a Maven project</a></li></ul></section><section>
<h2><a name="Resources_for_committers"></a>Resources for committers</h2>
<ul>
<li><a class="externalLink" href="http://www.apache.org/dev/"> Developer Resources</a></li>
@@ -171,7 +167,7 @@ Jason van Zyl" />
<li><a class="externalLink" href="http://www.apache.org/dev/committers.html"> Committer FAQ</a></li>
<li><a class="externalLink" href="http://status.apache.org/"> Web Stats</a></li>
<li><a class="externalLink" href="http://status.apache.org/"> Mailing List Stats</a></li>
-<li><a class="externalLink" href="http://wiki.apache.org/"> Apache Wiki</a></li></ul></div>
+<li><a class="externalLink" href="http://wiki.apache.org/"> Apache Wiki</a></li></ul></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/development/guide-maven-development.html
==============================================================================
--- maven/website/content/guides/development/guide-maven-development.html (original)
+++ maven/website/content/guides/development/guide-maven-development.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/development/guide-maven-development.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/development/guide-maven-development.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">
@@ -137,34 +137,29 @@ Maarten Mulders" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Developing_Maven"></a>Developing Maven</h2>
-<p>This document describes how to get started developing Maven itself. There is a separate page describing how to <a href="./guide-building-maven.html">build Maven</a>.</p>
-<div class="section">
+<p>This document describes how to get started developing Maven itself. There is a separate page describing how to <a href="./guide-building-maven.html">build Maven</a>.</p><section>
<h3><a name="Finding_some_work_to_do"></a>Finding some work to do</h3>
<p>First of all you need something to work on! Issues can be found in <a href="/issue-management.html">several JIRA projects</a>.</p>
<p>Another good place to look for work is the <a class="externalLink" href="https://s.apache.org/up-for-grabs_maven"> Up for grabs</a> list. This list contains relatively simple issues that can be worked on without a lot of prerequisite knowledge. </p>
-<p>When you find a issue you would like to work on, add a comment in the issue log so the core developers and other people looking for work know that someone is already working on it.</p></div>
-<div class="section">
+<p>When you find a issue you would like to work on, add a comment in the issue log so the core developers and other people looking for work know that someone is already working on it.</p></section><section>
<h3><a name="Where.27s_the_source.3F"></a>Where's the source?</h3>
-<p>See <a href="/scm.html">https://maven.apache.org/scm.html</a> for information. The Maven project uses the Apache GitBox Repositories, and all of them are dual-mirrored to <a class="externalLink" href="https://github.com/apache/"> GitHub</a>.</p></div>
-<div class="section">
+<p>See <a href="/scm.html">https://maven.apache.org/scm.html</a> for information. The Maven project uses the Apache GitBox Repositories, and all of them are dual-mirrored to <a class="externalLink" href="https://github.com/apache/"> GitHub</a>.</p></section><section>
<h3><a name="Don.27t_forget_tests.21"></a>Don't forget tests!</h3>
<p>You will find many unit tests. If at all possible, create or modify a unit test to demonstrate the problem, and then validate your fix.</p>
-<p>If the problem case can't be set up in the unit tests, add an integration test. Before submitting a patch, in any case, you should run all of the integration tests. The tests require an empty local repository. See <a href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more details.</p></div>
-<div class="section">
+<p>If the problem case can't be set up in the unit tests, add an integration test. Before submitting a patch, in any case, you should run all of the integration tests. The tests require an empty local repository. See <a href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more details.</p></section><section>
<h3><a name="Creating_and_submitting_a_patch">Creating and submitting a patch</a></h3>
<p>The most convenient way is to create a GitHub fork from the Git repository you are working with. When you have either completed an issue or just want some feedback on the work you have done, create a pull request. We have a couple of guidelines when submitting contributions:</p>
<ul>
-<li>Create your branch from <tt>master</tt>, not from a tag. Otherwise, your patch is outdated the moment you create it and might not be applicable to the development head.</li>
+<li>Create your branch from <code>master</code>, not from a tag. Otherwise, your patch is outdated the moment you create it and might not be applicable to the development head.</li>
<li>If this was a new piece of work without a JIRA issue, create a JIRA issue for it now.</li>
-<li>Name the branch after the issue number; the branch name would start with <tt><jira-project-id>-<ticket-id></tt>.</li>
+<li>Name the branch after the issue number; the branch name would start with <code><jira-project-id>-<ticket-id></code>.</li>
<li>Push your branch with the commit(s) to your fork.</li>
<li>Create a <a class="externalLink" href="https://help.github.com/en/articles/about-pull-requests"> pull request</a> to submit your contribution. Shortly after, someone will review the pull request and give you feedback on it.</li></ul>
<p>A short note:</p>
<ul>
-<li>Make sure that you follow our code style, see <a href="#Further_Links">Further Links</a>.</li></ul></div>
-<div class="section">
+<li>Make sure that you follow our code style, see <a href="#Further_Links">Further Links</a>.</li></ul></section><section>
<h3><a name="Pull_request_acceptance_criteria"></a>Pull request acceptance criteria</h3>
<p>There are a number of criteria that a pull request will be judged on:</p>
<ul>
@@ -172,8 +167,7 @@ Maarten Mulders" />
<li>Whether it fits the spirit of the project. Some pull requests may be rejected as they take the project in a different direction than the current development community has chosen. This is usually discussed on an issue well before a pull request is contributed, so if you are unsure, discuss it there or on the mailing lists first. Feel free to continue discussing it (with new justification) if you disagree, or appeal to a wider audience on the mailing lists.</li>
<li>Whether it contains tests. It is expected that any pull request relating to functionality will be accompanied by unit tests and/or integration tests. It is strongly desired (and will be requested) for bug fixes too, but will not be the basis for not applying it. At a bare minimum, the change should not decrease the amount of automated test coverage. As a community, we are focusing on increasing the current coverage, as there are several areas that do not receive automated testing.</li>
<li>Whether it contains documentation. All new functionality needs to be documented for users, even if it is very rough for someone to expand on later. While rough is acceptable, incomplete is not. As with automated testing, as a community we are striving to increase the current coverage of documentation.</li></ul>
-<p>Above all, don't be discouraged. These are the same requirements the current committers should hold each other to as well. And remember, your contributions are always welcome!</p></div>
-<div class="section">
+<p>Above all, don't be discouraged. These are the same requirements the current committers should hold each other to as well. And remember, your contributions are always welcome!</p></section><section>
<h3><a name="Related_Projects"></a>Related Projects</h3>
<p>Maven has a few dependencies on other projects.</p>
<ul>
@@ -185,8 +179,7 @@ Maarten Mulders" />
<p>You can <a class="externalLink" href="https://codehaus-plexus.github.io/modello/">read more about Modello</a>.</p></li>
<li><b>Mojo</b>
<p>"Mojo" is really two things when it comes to Maven: it is both <a href="/ref/current/maven-plugin-api/">Maven's plug-in API</a> and also <a class="externalLink" href="http://www.mojohaus.org">a separate Mojohaus project</a> hosting a lot of plugins.</p>
-<p><a class="externalLink" href="http://www.mojohaus.org">The MojoHaus Project</a> is a plugin forge for non-core Maven plugins. There is also a lower bar for becoming a part of the project.</p></li></ul></div>
-<div class="section">
+<p><a class="externalLink" href="http://www.mojohaus.org">The MojoHaus Project</a> is a plugin forge for non-core Maven plugins. There is also a lower bar for becoming a part of the project.</p></li></ul></section><section>
<h3><a name="Sub_Projects"></a>Sub Projects</h3>
<ul>
<li>Maven Surefire
@@ -200,13 +193,12 @@ Maarten Mulders" />
<p>You can <a href="/scm/">read more about Scm</a>.</p></li>
<li>Maven Wagon
<p>Maven Wagon is a standalone API that deals with transporting files and directories. Maven Core uses the Wagon API to download and upload artifacts and artifact metadata. The site plug-in uses it to publish the site.</p>
-<p>You can <a href="/wagon/">read more about Wagon</a>.</p></li></ul></div>
-<div class="section">
+<p>You can <a href="/wagon/">read more about Wagon</a>.</p></li></ul></section><section>
<h3><a name="Further_Links">Further Links</a></h3>
<ul>
<li><a href="../../developers/conventions/code.html">Maven Code Style And Code Convention</a></li>
<li><a href="../../developers/conventions/jira.html">Maven JIRA Convention</a></li>
-<li><a href="../../developers/conventions/svn.html">Maven SVN Convention</a></li></ul></div></div>
+<li><a href="../../developers/conventions/svn.html">Maven SVN Convention</a></li></ul></section></section>
</div>
</div>
</div>