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 [1/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...
Author: svn-site-role
Date: Sun Jun 9 13:59:34 2019
New Revision: 1860906
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/about.html
maven/website/content/aether.html
maven/website/content/apache-resource-bundles/index.html
maven/website/content/archives/maven-2.x/index.html
maven/website/content/articles.html
maven/website/content/background/history-of-maven.html
maven/website/content/background/philosophy-of-maven.html
maven/website/content/ci-management.html
maven/website/content/code-quality-management.html
maven/website/content/community.html
maven/website/content/configure.html
maven/website/content/continuous-integration.html
maven/website/content/developers/committer-environment.html
maven/website/content/developers/committer-settings.html
maven/website/content/developers/conventions/code.html
maven/website/content/developers/conventions/git.html
maven/website/content/developers/conventions/jira.html
maven/website/content/developers/dependency-policies.html
maven/website/content/developers/index.html
maven/website/content/developers/java6.html
maven/website/content/developers/mojo-api-specification.html
maven/website/content/developers/release/index.html
maven/website/content/developers/release/maven-core-release.html
maven/website/content/developers/release/maven-project-release-procedure.html
maven/website/content/developers/release/parent-pom-release.html
maven/website/content/developers/release/pmc-gpg-keys.html
maven/website/content/developers/retirement-plan-plugins.html
maven/website/content/developers/website/component-reference-documentation-helper.html
maven/website/content/developers/website/deploy-component-reference-documentation.html
maven/website/content/developers/website/deploy-maven-website.html
maven/website/content/developers/website/index.html
maven/website/content/developers/website/website-overview.html
maven/website/content/developers/welcome-to-new-committers.html
maven/website/content/docs-required.html
maven/website/content/docs/2.0.1/release-notes.html
maven/website/content/docs/2.0.10/release-notes.html
maven/website/content/docs/2.0.11/release-notes.html
maven/website/content/docs/2.0.2/release-notes.html
maven/website/content/docs/2.0.3/release-notes.html
maven/website/content/docs/2.0.4/release-notes.html
maven/website/content/docs/2.0.5/release-notes.html
maven/website/content/docs/2.0.6/release-notes.html
maven/website/content/docs/2.0.7/release-notes.html
maven/website/content/docs/2.0.8/release-notes.html
maven/website/content/docs/2.0.9/release-notes.html
maven/website/content/docs/2.0/release-notes.html
maven/website/content/docs/2.1.0/release-notes.html
maven/website/content/docs/2.2.0/release-notes.html
maven/website/content/docs/2.2.1/release-notes.html
maven/website/content/docs/3.0-alpha-3/release-notes.html
maven/website/content/docs/3.0-alpha-4/release-notes.html
maven/website/content/docs/3.0-alpha-5/release-notes.html
maven/website/content/docs/3.0-alpha-6/release-notes.html
maven/website/content/docs/3.0-alpha-7/release-notes.html
maven/website/content/docs/3.0-beta-1/release-notes.html
maven/website/content/docs/3.0-beta-2/release-notes.html
maven/website/content/docs/3.0-beta-3/release-notes.html
maven/website/content/docs/3.0.1/release-notes.html
maven/website/content/docs/3.0.2/release-notes.html
maven/website/content/docs/3.0.3/release-notes.html
maven/website/content/docs/3.0.4/release-notes.html
maven/website/content/docs/3.0.5/release-notes.html
maven/website/content/docs/3.0/release-notes.html
maven/website/content/docs/3.1.0-alpha-1/release-notes.html
maven/website/content/docs/3.1.0/release-notes.html
maven/website/content/docs/3.1.1/release-notes.html
maven/website/content/docs/3.2.1/release-notes.html
maven/website/content/docs/3.2.2/release-notes.html
maven/website/content/docs/3.2.3/release-notes.html
maven/website/content/docs/3.2.5/release-notes.html
maven/website/content/docs/3.3.1/release-notes.html
maven/website/content/docs/3.3.3/release-notes.html
maven/website/content/docs/3.3.9/release-notes.html
maven/website/content/docs/3.5.0-alpha-1/release-notes.html
maven/website/content/docs/3.5.0-beta-1/release-notes.html
maven/website/content/docs/3.5.0/release-notes.html
maven/website/content/docs/3.5.2/release-notes.html
maven/website/content/docs/3.5.3/release-notes.html
maven/website/content/docs/3.5.4/release-notes.html
maven/website/content/docs/3.6.0/release-notes.html
maven/website/content/docs/3.6.1/release-notes.html
maven/website/content/docs/history.html
maven/website/content/download.html
maven/website/content/errors/404.html
maven/website/content/examples/index.html
maven/website/content/examples/injecting-properties-via-settings.html
maven/website/content/examples/maven-3-lifecycle-extensions.html
maven/website/content/general.html
maven/website/content/glossary.html
maven/website/content/guides/development/guide-building-maven.html
maven/website/content/guides/development/guide-committer-school.html
maven/website/content/guides/development/guide-documentation-style.html
maven/website/content/guides/development/guide-helping.html
maven/website/content/guides/development/guide-maven-development.html
maven/website/content/guides/development/guide-plugin-documentation.html
maven/website/content/guides/development/guide-testing-development-plugins.html
maven/website/content/guides/development/guide-testing-releases.html
maven/website/content/guides/getting-started/index.html
maven/website/content/guides/getting-started/maven-in-five-minutes.html
maven/website/content/guides/getting-started/windows-prerequisites.html
maven/website/content/guides/index.html
maven/website/content/guides/introduction/introduction-to-archetypes.html
maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html
maven/website/content/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
maven/website/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
maven/website/content/guides/introduction/introduction-to-plugins.html
maven/website/content/guides/introduction/introduction-to-profiles.html
maven/website/content/guides/introduction/introduction-to-repositories.html
maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
maven/website/content/guides/introduction/introduction-to-the-pom.html
maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html
maven/website/content/guides/mini/guide-3rd-party-jars-local.html
maven/website/content/guides/mini/guide-3rd-party-jars-remote.html
maven/website/content/guides/mini/guide-archive-configuration.html
maven/website/content/guides/mini/guide-assemblies.html
maven/website/content/guides/mini/guide-attached-tests.html
maven/website/content/guides/mini/guide-bash-m2-completion.html
maven/website/content/guides/mini/guide-building-for-different-environments.html
maven/website/content/guides/mini/guide-building-jdk14-on-jdk15.html
maven/website/content/guides/mini/guide-configuring-maven.html
maven/website/content/guides/mini/guide-configuring-plugins.html
maven/website/content/guides/mini/guide-coping-with-sun-jars.html
maven/website/content/guides/mini/guide-creating-archetypes.html
maven/website/content/guides/mini/guide-default-execution-ids.html
maven/website/content/guides/mini/guide-deployment-security-settings.html
maven/website/content/guides/mini/guide-encryption.html
maven/website/content/guides/mini/guide-generating-sources.html
maven/website/content/guides/mini/guide-http-settings.html
maven/website/content/guides/mini/guide-manifest.html
maven/website/content/guides/mini/guide-maven-classloading.html
maven/website/content/guides/mini/guide-mirror-settings.html
maven/website/content/guides/mini/guide-multiple-modules.html
maven/website/content/guides/mini/guide-multiple-repositories.html
maven/website/content/guides/mini/guide-naming-conventions.html
maven/website/content/guides/mini/guide-new-committers.html
maven/website/content/guides/mini/guide-proxies.html
maven/website/content/guides/mini/guide-releasing.html
maven/website/content/guides/mini/guide-relocation.html
maven/website/content/guides/mini/guide-repository-ssl.html
maven/website/content/guides/mini/guide-site.html
maven/website/content/guides/mini/guide-snippet-macro.html
maven/website/content/guides/mini/guide-using-ant.html
maven/website/content/guides/mini/guide-using-extensions.html
maven/website/content/guides/mini/guide-using-modello.html
maven/website/content/guides/mini/guide-using-one-source-directory.html
maven/website/content/guides/mini/guide-using-toolchains.html
maven/website/content/guides/mini/guide-wagon-providers.html
maven/website/content/guides/mini/index.html
maven/website/content/guides/plugin/guide-java-plugin-development.html
maven/website/content/guides/plugin/guide-java-report-plugin-development.html
maven/website/content/ide.html
maven/website/content/index.html
maven/website/content/install.html
maven/website/content/issue-management.html
maven/website/content/mailing-lists.html
maven/website/content/maven-1.x-eol.html
maven/website/content/maven-2.x-eol.html
maven/website/content/maven-ci-friendly.html
maven/website/content/maven-conventions.html
maven/website/content/maven-features.html
maven/website/content/maven-jsr330.html
maven/website/content/maven-logging.html
maven/website/content/maven-site-1.0-site.jar
maven/website/content/maven1.html
maven/website/content/plugin-developers/common-bugs.html
maven/website/content/plugin-developers/cookbook/add-build-time-to-manifest.html
maven/website/content/plugin-developers/cookbook/add-svn-revision-to-manifest.html
maven/website/content/plugin-developers/cookbook/attach-source-javadoc-artifacts.html
maven/website/content/plugin-developers/cookbook/generate-assembly.html
maven/website/content/plugin-developers/cookbook/index.html
maven/website/content/plugin-developers/cookbook/plexus-plugin-upgrade.html
maven/website/content/plugin-developers/index.html
maven/website/content/plugin-developers/plugin-documenting.html
maven/website/content/plugin-developers/plugin-testing.html
maven/website/content/plugins/index.html
maven/website/content/plugins/localization.html
maven/website/content/pom.html
maven/website/content/pom/index.html
maven/website/content/privacy-policy.html
maven/website/content/project-faq.html
maven/website/content/project-info.html
maven/website/content/project-roles.html
maven/website/content/reference/maven-classloading.html
maven/website/content/release-notes-all.html
maven/website/content/repository-management.html
maven/website/content/repository/central-index.html
maven/website/content/repository/central-metadata.html
maven/website/content/repository/guide-central-repository-upload.html
maven/website/content/repository/index.html
maven/website/content/run-maven/index.html
maven/website/content/run.html
maven/website/content/scm.html
maven/website/content/security-plexus-archiver.html
maven/website/content/security.html
maven/website/content/settings.html
maven/website/content/shared/index.html
maven/website/content/skins/index.html
maven/website/content/support-and-training.html
maven/website/content/team.html
maven/website/content/testimonials.html
maven/website/content/users/getting-help.html
maven/website/content/users/index.html
maven/website/content/what-is-maven.html
Modified: maven/website/content/about.html
==============================================================================
--- maven/website/content/about.html (original)
+++ maven/website/content/about.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/about.fml at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/fml/about.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">
@@ -118,14 +118,14 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="About_Maven_2.0"></a><a name="top">About Maven 2.0</a></h2>
<ol style="list-style-type: decimal">
<li><a href="#m2-goals">Tell me about the goals of Maven 2.0</a></li>
<li><a href="#m3-goals">Tell me about the goals of Maven 3.0</a></li>
<li><a href="#get-involved">Can I get involved?</a></li>
<li><a href="#scripting-languages">What plugin languages will Maven 2.0 support? What about [insert language here]?</a></li>
-<li><a href="#get-help">Where do I get help with Maven 2 & 3?</a></li></ol></div>
+<li><a href="#get-help">Where do I get help with Maven 2 & 3?</a></li></ol></section>
<dl>
<dt><a name="m2-goals">Tell me about the goals of Maven 2.0</a></dt>
<dd>
@@ -242,10 +242,10 @@
</p>
<p>
- You can also join us on IRC (Internet Relay Chat) at <tt>irc.freenode.net</tt>
- on <tt>#maven</tt>.
+ You can also join us on IRC (Internet Relay Chat) at <code>irc.freenode.net</code>
+ on <code>#maven</code>.
over <a class="externalLink" href="irc://irc.freenode.net/#maven">IRC</a>
- for those behind firewalls (enter <tt>#maven</tt> in the <i>Channel</i> box).
+ for those behind firewalls (enter <code>#maven</code> in the <i>Channel</i> box).
</p>
<p align="right"><a href="#top">[top]</a></p></dd></dl>
Modified: maven/website/content/aether.html
==============================================================================
--- maven/website/content/aether.html (original)
+++ maven/website/content/aether.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/aether.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/aether.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,11 +118,9 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<h1>Aether import plan to Maven</h1>
-<div class="section">
+<h1>Aether import plan to Maven</h1><section>
<h2><a name="IP_Clearance"></a>IP Clearance</h2>
-<p>Tracked on <a class="externalLink" href="http://incubator.apache.org/ip-clearance/maven-aether.html">Incubator IP Clearance</a> and through <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6007">MNG-6007</a>.</p></div>
-<div class="section">
+<p>Tracked on <a class="externalLink" href="http://incubator.apache.org/ip-clearance/maven-aether.html">Incubator IP Clearance</a> and through <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6007">MNG-6007</a>.</p></section><section>
<h2><a name="Code_integration"></a>Code integration</h2>
<table border="0" class="table table-striped">
<thead>
@@ -190,8 +188,7 @@
<td><a class="externalLink" href="http://maven.apache.org/ref/3.3.9/maven-aether-provider/">Maven Aether Provider</a></td>
<td><a class="externalLink" href="https://maven.apache.org/ref/3.6.1/maven-resolver-provider/">Maven Resolver Provider</a></td></tr>
</tbody>
-</table></div>
-<div class="section">
+</table></section><section>
<h2><a name="Versions_history"></a>Versions history</h2>
<table border="0" class="table table-striped">
<thead>
@@ -229,7 +226,7 @@
<td>Eclipse Aether 1.0.2.v20150114</td>
<td>2015-03-18 <a class="externalLink" href="http://maven.apache.org/ref/3.3.1/apache-maven/dependencies.html">3.3.1</a><br />2015-04-28 <a class="externalLink" href="http://maven.apache.org/ref/3.3.3/apache-maven/dependencies.html">3.3.3</a><br />2015-11-14 <a class="externalLink" href="http://maven.apache.org/ref/3.3.9/apache-maven/dependencies.html">3.3.9</a></td></tr>
</tbody>
-</table></div>
+</table></section>
</div>
</div>
</div>
Modified: maven/website/content/apache-resource-bundles/index.html
==============================================================================
--- maven/website/content/apache-resource-bundles/index.html (original)
+++ maven/website/content/apache-resource-bundles/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/xdoc/apache-resource-bundles/index.xml at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/xdoc/apache-resource-bundles/index.xml 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,7 +121,7 @@
<div id="bodyColumn" class="span10" >
- <div class="section">
+ <section>
<h2><a name="Apache_Resource_Bundles"></a>Apache Resource Bundles</h2>
<p>Maven project provides a set of resources to help you build Java resources compliant with Apache rules.</p>
@@ -132,8 +132,7 @@
<a class="externalLink" href="https://issues.apache.org/jira/browse/MASFRES/">JIRA</a>.
</p>
-
-<div class="section">
+ <section>
<h2><a name="JAR_Resource_Bundle_and_Incubator_Disclaimer_Resource_Bundle"></a>JAR Resource Bundle and Incubator Disclaimer Resource Bundle</h2>
<p>
@@ -141,13 +140,13 @@
</p>
<ul>
-<li><tt>META-INF/DEPENDENCIES</tt></li>
+<li>META-INF/DEPENDENCIES</li>
-<li><tt>META-INF/LICENSE</tt></li>
+<li>META-INF/LICENSE</li>
-<li><tt>META-INF/NOTICE</tt></li>
+<li>META-INF/NOTICE</li>
-<li><tt>META-INF/DISCLAIMER</tt></li>
+<li>META-INF/DISCLAIMER</li>
</ul>
<div class="source"><pre class="prettyprint linenums"> <plugin>
@@ -173,10 +172,9 @@
</executions>
</plugin></pre></div>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h2><a name="Source_Release_Assembly_Descriptor"></a>Source Release Assembly Descriptor</h2>
<p>Create a source-release artifact that contains the fully buildable project directory source structure.
@@ -220,8 +218,8 @@
</executions>
</plugin></pre></div>
- </div>
- </div>
+ </section>
+ </section>
</div>
Modified: maven/website/content/archives/maven-2.x/index.html
==============================================================================
--- maven/website/content/archives/maven-2.x/index.html (original)
+++ maven/website/content/archives/maven-2.x/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/archives/maven-2.x/index.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/archives/maven-2.x/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,10 +120,9 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="This_is_the_Maven_2_Graveyard"></a>This is the Maven 2 Graveyard</h2>
-<p>Based on a decision for the End Of Lifetime of Maven 2 this location is intended as a graveyard for Maven 2 only related information and links.</p>
-<div class="section">
+<p>Based on a decision for the End Of Lifetime of Maven 2 this location is intended as a graveyard for Maven 2 only related information and links.</p><section>
<h3><a name="Plugin_List"></a>Plugin List</h3>
<p>The following list of plugins contains plugins which are Maven 2 specific. Apart from that for those plugins which are listed here there are no updates/bug fixes planned etc.</p>
<table border="1" class="table table-striped">
@@ -142,13 +141,13 @@
<td align="left"><b>Plugins corresponding to default core phases (ie. clean, compile). They may have multiple goals as well.</b></td>
<td align="left"></td></tr>
<tr class="a">
-<td align="left"><a href="/plugins/maven-reactor-plugin/"> <tt>reactor</tt></a></td>
+<td align="left"><a href="/plugins/maven-reactor-plugin/"> <code>reactor</code></a></td>
<td align="left">B</td>
<td align="left">1.0</td>
<td align="left">2008-09-27</td>
<td align="left">Build a subset of interdependent projects in a reactor</td>
<td align="left">2014-03-24</td></tr></table>
-<p>* <b>B</b>uild or <b>R</b>eporting plugin</p></div></div>
+<p>* <b>B</b>uild or <b>R</b>eporting plugin</p></section></section>
</div>
</div>
</div>
Modified: maven/website/content/articles.html
==============================================================================
--- maven/website/content/articles.html (original)
+++ maven/website/content/articles.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/articles.xml at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/xdoc/articles.xml at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -122,7 +122,7 @@
<div id="bodyColumn" class="span10" >
- <div class="section">
+ <section>
<h2><a name="Books_on_Maven"></a>Books on Maven</h2>
@@ -309,20 +309,18 @@ Eric Redmond)
</ul>
</div>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h2><a name="Miscellaneous_on_Maven"></a>Miscellaneous on Maven</h2>
<p>
If you're interested in testing your Maven skills, check out <a class="externalLink" href="http://www.javablackbelt.com/QuestionnaireDefDisplay.wwa?questPublicId=01559">JavaBlackBelt's Maven exam</a>.
This exam is being written collaboratively by the community. Feel free to add new questions, suggest improvements, etc.
</p>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h2><a name="Articles_on_Maven"></a>Articles on Maven</h2>
<p>
@@ -725,7 +723,7 @@ Eric Redmond)
</tr>
</table>
</div>
- </div>
+ </section>
</div>
Modified: maven/website/content/background/history-of-maven.html
==============================================================================
--- maven/website/content/background/history-of-maven.html (original)
+++ maven/website/content/background/history-of-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/markdown/background/history-of-maven.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/background/history-of-maven.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">
@@ -123,8 +123,7 @@
Jason van Zyl
12 October 2005
-->
-
-<div class="section">
+<section>
<h2><a name="History_of_Maven_by_Jason_van_Zyl"></a>History of Maven by Jason van Zyl</h2>
<p>Maven began its life in the <a class="externalLink" href="http://jakarta.apache.org">Jakarta</a> <a class="externalLink" href="http://jakarta.apache.org/alexandria/legacy/">Alexandria</a> project. The Alexandria project is now defunct but was the breeding ground for not only Maven, but for the <a class="externalLink" href="http://gump.apache.org">Gump</a> and <a class="externalLink" href="http://forrest.apache.org">Forrest</a> projects as well. The first import of prototype sources happened in <a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200108.mbox/%3c20010827163505.53005.qmail@icarus.apache.org%3e">August 2001</a>. As of the date of this document (October 2005) Maven was <a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200202.mbox/%3c20020202153719.50163.qmail@icarus.apache.org%3e">removed</a> from Alexandria about 3 years, 7 months ago making Maven about 4 years old! Maven spent about
5 months as part of the Alexandria before moving on to its next home in the <a class="externalLink" href="http://turbine.apache.org/">Turbine</a> project.</p>
<p>Though Maven started in Alexandria the test bed for its use was the Turbine project. Turbine was in the process of decoupling its persistence layer, services layer and web layer into separate builds and I got very tired of having to maintain several different builds which were essentially the same. There was no way to easy template Ant builds in those days and every ant build appeared to be different and I found this incredibly frustrating and futile. I figured who really cares how the build works so long as it works and is easy to use. The infrastructure of a project is incredibly important but the value of a project lies in the application being developed. As such the build is generally neglected and tends to fall apart when you need it to work most like when you need to prepare a release or when more then a couple of people are working on the project. In Jakarta land four years ago it was rare that a Ant build worked out of the box. Mind you many Turbine developers suffered as
I tried to get Maven working which is something I regret, but I figure how do new projects start and survive if someone doesn’t suffer. I figured it was for their own good (I’ve been known to have an opinion or two) and after much gnashing of teeth I think Maven has finally come of age. It reminds me of one of my favourite quotes from Ralph Johnson and Don Roberts in Patterns for Evolving Frameworks:</p>
@@ -142,7 +141,7 @@
<p>As noted above one of the projects in Alexandria at the time was Gump. Sam Ruby tried to convince me that using the Gump model would be a good idea so I took a look. After taking a look at the descriptors I noted that Gump pretty much allowed any project to do whatever it wanted in terms of directory structure, use of JARs in CVS, multiple artifacts per project, documentation splayed everywhere, and several other things that made no sense to me as Gump was not trying to standardize anything at the time but trying to continuously integrate anything it could get its hands on. My goals were different and I wanted to make an <a class="externalLink" href="http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html">opinionated</a> piece of software and I preferred the notion of convention over configuration. I wanted a project’s infrastructure to look the same and work the same so I continued to pursue my own model for a project and decided to di
sagree with Gump’s particular tact at project modeling which I thought was too flexible. I wanted to save people time by being able to find things in the same place. Again the value in a project is the final result: how it is constructed and built predictable and easy. I fully admit some warts in Maven 1.x sometimes made things harder but that is par for the course with first generation tools.</p>
<p>The next thing I noticed were all the JARs that we were depending on were stored in CVS. We had many copies of Xerces laying around which is a waste of space, every time the version of Xerces changed I had to update the copies of Xerces in each of the projects, but more importantly without some declarative statement of your dependencies there is no way you could perform any analysis. People tend to miss the point entirely regarding a declarative dependency use. People say it’s so easy just to store their dependencies in an SCM but try decomposing your big crappy build into components to encourage reuse and ease of maintenance, or try to analyze what you might need at runtime between all your different apps with commons dependencies in the graph and you’re shit out of luck. The true power of declarative dependencies lies not in the fact that you can save a few bytes of disk space, though it can really add up if you’re not careful, but in the analysis that can
be performed. Once you have a decent graph all sorts of things are possible. Back to history: so now that declarative dependencies existed it needed to be easier …</p>
<p>This is when I decided to employ standard Java-like inheritance in the model used and find a way to create a repository for things you need to build. So I hacked in some inheritance goop and now it was time for the repository. I asked around Apache to see if it would be possible to host a repository and soon found out that it was not possible to host non-Apache-like artifacts. So LGPL and GPL artifacts were out which didn’t really make for a useful repository. After a little hunting I found <a class="externalLink" href="http://www.ibiblio.org">Ibiblio</a> which is a vast archive of all sorts of neat stuff including tons of free software. One of the mandates of Ibiblio is to aid in the dispersal of free software. Sounded perfect to me so I got in contact with John Reuning at Ibiblio and the rest is history. Working with the folks at Ibiblio has been a pleasure, the admins there are an amazingly helpful and talented bunch. They let us store whatever free software we want, pr
ovide great stats, and will let us host any software we want. Ibiblio is very cool.</p>
-<p>Many people had some problems with Maven 1.x but it generally worked and all tools in their first generation suffer from many short comings and the only way to overcome that is to forge ahead and try to create something better the next time around. With all the feed back the Maven developers have received from 1.x users and during the betas of 2.0 we think we’ve finally got something to build on. The first version of Maven was written by myself with lots of help from Bob McWhirter</p></div>
+<p>Many people had some problems with Maven 1.x but it generally worked and all tools in their first generation suffer from many short comings and the only way to overcome that is to forge ahead and try to create something better the next time around. With all the feed back the Maven developers have received from 1.x users and during the betas of 2.0 we think we’ve finally got something to build on. The first version of Maven was written by myself with lots of help from Bob McWhirter</p></section>
</div>
</div>
</div>
Modified: maven/website/content/background/philosophy-of-maven.html
==============================================================================
--- maven/website/content/background/philosophy-of-maven.html (original)
+++ maven/website/content/background/philosophy-of-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/markdown/background/philosophy-of-maven.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/background/philosophy-of-maven.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">
Modified: maven/website/content/ci-management.html
==============================================================================
--- maven/website/content/ci-management.html (original)
+++ maven/website/content/ci-management.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 org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.0:ci-management at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.0:ci-management 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">
@@ -127,14 +127,12 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Overview"></a>Overview</h2><a name="Overview"></a>
-<p>This project uses <a class="externalLink" href="http://jenkins-ci.org/">Jenkins</a>.</p></div>
-<div class="section">
+<p>This project uses <a class="externalLink" href="http://jenkins-ci.org/">Jenkins</a>.</p></section><section>
<h2><a name="Access"></a>Access</h2><a name="Access"></a>
<p>The following is a link to the continuous integration system used by the project:</p>
-<div class="source"><pre class="prettyprint linenums"><a class="externalLink" href="https://builds.apache.org/view/M-R/view/Maven/job/maven-box/">https://builds.apache.org/view/M-R/view/Maven/job/maven-box/</a></pre></div></div>
-<div class="section">
+<div class="source"><pre class="prettyprint linenums"><a class="externalLink" href="https://builds.apache.org/view/M-R/view/Maven/job/maven-box/">https://builds.apache.org/view/M-R/view/Maven/job/maven-box/</a></pre></div></section><section>
<h2><a name="Notifiers"></a>Notifiers</h2><a name="Notifiers"></a>
<p>Configuration for notifying developers/users when a build is unsuccessful, including user information and notification mode.</p>
<table border="0" class="table table-striped">
@@ -145,7 +143,7 @@
<tr class="b">
<td>mail</td>
<td>-</td>
-<td>address=notifications@maven.apache.org</td></tr></table></div>
+<td>address=notifications@maven.apache.org</td></tr></table></section>
</div>
</div>
</div>
Modified: maven/website/content/code-quality-management.html
==============================================================================
--- maven/website/content/code-quality-management.html (original)
+++ maven/website/content/code-quality-management.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/code-quality-management.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/code-quality-management.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,10 +118,9 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Code_Quality_Management"></a>Code Quality Management</h2>
-<p>Some existing Maven plugins use code analysis technologies (like <a class="externalLink" href="https://maven.apache.org/plugins/maven-checkstyle-plugin/">Checkstyle</a>, <a class="externalLink" href="https://maven.apache.org/plugins/maven-pmd-plugin/">PMD</a>, <a class="externalLink" href="https://mojohaus.org/jdepend-maven-plugin/">JDepend</a>, …) to generate various quality reports. This page lists technologies and platforms that know how to aggregate all this information to offer enhanced quality management functionalities.</p>
-<div class="section">
+<p>Some existing Maven plugins use code analysis technologies (like <a class="externalLink" href="https://maven.apache.org/plugins/maven-checkstyle-plugin/">Checkstyle</a>, <a class="externalLink" href="https://maven.apache.org/plugins/maven-pmd-plugin/">PMD</a>, <a class="externalLink" href="https://mojohaus.org/jdepend-maven-plugin/">JDepend</a>, …) to generate various quality reports. This page lists technologies and platforms that know how to aggregate all this information to offer enhanced quality management functionalities.</p><section>
<h3><a name="Quality_management_technologies_and_platforms"></a>Quality management technologies and platforms</h3>
<p>Following is an alphabetical list of those we’ve heard mentioned around the Maven community:</p>
<ul>
@@ -131,7 +130,7 @@
<li><a class="externalLink" href="http://www.sonarqube.org/">SonarQube</a></li>
<li><a class="externalLink" href="http://www.squale.org/">Squale</a></li>
<li><a class="externalLink" href="http://xradar.sourceforge.net">XRadar</a></li>
-</ul></div></div>
+</ul></section></section>
</div>
</div>
</div>
Modified: maven/website/content/community.html
==============================================================================
--- maven/website/content/community.html (original)
+++ maven/website/content/community.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/community.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/community.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,38 +118,29 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="The_Maven_Community"></a>The Maven Community</h2>
-<p>Maven, like any other opensource project, relies heavily on the efforts of the entire user community to be ever vigilant for improvements, logging of defects, communicating use-cases, generating documentation, and being wary of other users in need. This is a quick guide outlining what members of the Maven community may do to make the system work better for everyone.</p>
-<div class="section">
+<p>Maven, like any other opensource project, relies heavily on the efforts of the entire user community to be ever vigilant for improvements, logging of defects, communicating use-cases, generating documentation, and being wary of other users in need. This is a quick guide outlining what members of the Maven community may do to make the system work better for everyone.</p><section>
<h3><a name="Helping_With_Maven"></a>Helping With Maven</h3>
-<p>There is already a comprehensive <a href="./guides/development/guide-helping.html">Guide to Helping With Maven</a>. That guide focuses upon beginning as a supporter, with information on how to help the coding effort.</p>
-<div class="section">
+<p>There is already a comprehensive <a href="./guides/development/guide-helping.html">Guide to Helping With Maven</a>. That guide focuses upon beginning as a supporter, with information on how to help the coding effort.</p><section>
<h4><a name="Commit_Questions_or_Answers_to_the_Maven_User_FAQ"></a>Commit Questions or Answers to the Maven User FAQ</h4>
-<p>If you find things which are not correct or could be explained in a better way or you simply miss things do not hesitate to contact the maven community via the users mailing list and tell us about it.</p></div>
-<div class="section">
+<p>If you find things which are not correct or could be explained in a better way or you simply miss things do not hesitate to contact the maven community via the users mailing list and tell us about it.</p></section><section>
<h4><a name="Help_Log_Defects_in_JIRA"></a>Help Log Defects in JIRA</h4>
-<p>Just as any other healthy project requires a quick turn-around on defects, and a transparent method of users to have their wishes heard, so too does Maven need your help. Refer to the <a href="./issue-management.html">Issue Management</a> page.</p></div>
-<div class="section">
+<p>Just as any other healthy project requires a quick turn-around on defects, and a transparent method of users to have their wishes heard, so too does Maven need your help. Refer to the <a href="./issue-management.html">Issue Management</a> page.</p></section><section>
<h4><a name="Developers"></a>Developers</h4>
-<p>For Maven developers, committers, PMC: there is a <a href="./developers/index.html">Developers Guide</a>.</p></div></div>
-<div class="section">
+<p>For Maven developers, committers, PMC: there is a <a href="./developers/index.html">Developers Guide</a>.</p></section></section><section>
<h3><a name="Being_a_Good_Maven_Citizen"></a>Being a Good Maven Citizen</h3>
-<p>The concept of a public repository built into the core architecture of Maven makes it necessarily community-centric. There are a few simple things that Maven users may do to help keep that community thriving.</p>
-<div class="section">
+<p>The concept of a public repository built into the core architecture of Maven makes it necessarily community-centric. There are a few simple things that Maven users may do to help keep that community thriving.</p><section>
<h4><a name="Be_a_Kind_Public_Repository_User"></a>Be a Kind Public Repository User</h4>
<p>The best thing that a user can do is to set up their own remote repository mirror containing the projects needed: this is called a <a href=".//repository-management.html">repository manager</a>. This reduces strain on the Maven central repository, and allows new users to get acquainted with Maven easier and quicker. This is especially important for power-users and corporations. The incentive behind this is, controlling your own servers can give you desired level of security and more control over uptime, resulting in a better experience for your users. With that said, keep the following sentiment in mind:</p>
<p><i>DO NOT wget THE ENTIRE REPOSITORY!</i></p>
-<p>Please take only the jars you need. We understand this is may entail more work, but grabbing more than 1,7 TiB of binaries really kills our servers.</p></div></div>
-<div class="section">
+<p>Please take only the jars you need. We understand this is may entail more work, but grabbing more than 1,7 TiB of binaries really kills our servers.</p></section></section><section>
<h3><a name="User_Gathering_Spots"></a>User Gathering Spots</h3>
-<p>These are a few of the watering holes around which Maven users tend to gather.</p>
-<div class="section">
+<p>These are a few of the watering holes around which Maven users tend to gather.</p><section>
<h4><a name="Mailing_Lists"></a>Mailing Lists</h4>
-<p>Maven has a number of <a href="./mailing-lists.html">Mailing Lists</a>, and the Maven User List is specifically dedicated to answering questions about all Maven things.</p></div>
-<div class="section">
+<p>Maven has a number of <a href="./mailing-lists.html">Mailing Lists</a>, and the Maven User List is specifically dedicated to answering questions about all Maven things.</p></section><section>
<h4><a name="IRC_.28Internet_Relay_Chat.29"></a>IRC (Internet Relay Chat)</h4>
-<p>Log into the <tt>#maven</tt> IRC channel on <tt>irc.freenode.net</tt> with your favorite IRC client or <a class="externalLink" href="https://webchat.freenode.net/">with web IRC chat</a>.</p></div></div></div>
+<p>Log into the #maven IRC channel on irc.freenode.net with your favorite IRC client or <a class="externalLink" href="https://webchat.freenode.net/">with web IRC chat</a>.</p></section></section></section>
</div>
</div>
</div>
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.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/configure.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/configure.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">
@@ -127,21 +127,17 @@
</div>
<div id="bodyColumn" class="span10" >
<h1>Configuring Apache Maven</h1>
-<p>The configuration for Apache Maven usage itself and projects built with resides in a number of places:</p>
-<div class="section">
-<h2><a name="MAVEN_OPTS_environment_variable:"></a><tt>MAVEN_OPTS</tt> environment variable:</h2>
-<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to globally to Maven. E.g. JVM memory settings could be defined with the value <tt>-Xms256m -Xmx512m</tt>.</p></div>
-<div class="section">
-<h2><a name="settings.xml_file:"></a><tt>settings.xml</tt> file:</h2>
-<p>Located in USER_HOME/.m2 the settings files is designed to contain any configuration for Maven usage across projects.</p></div>
-<div class="section">
-<h2><a name="a.mvn_folder:"></a><tt>.mvn</tt> folder:</h2>
-<p>Located with in the projects top level folder, the files <tt>maven.config</tt>, <tt>jvm.config</tt>, and <tt>extensions.xml</tt> contain project specific configuration for running Maven.</p>
-<p>This folder is part of the project and may be checked in into your version control.</p>
-<div class="section">
-<h3><a name="a.mvn.2Fextensions.xml_file:"></a><tt>.mvn/extensions.xml</tt> file:</h3>
-<p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you have other dependencies) which contains the extension and put it manually into the <tt>${MAVEN_HOME}/lib/ext</tt> folder. This means you had to change the Maven installation. The consequence was that everyone who likes to use this needed to change it’s installation and makes the on-boarding for a developer much more inconvenient. The other option was to give the path to the jar on command line via <tt>mvn -Dmaven.ext.class.path=extension.jar</tt>. This has the drawback giving those options to your Maven build every time you are calling Maven. Not very convenient as well.</p>
-<p>From now on this can be done much more simpler and in a more Maven like way. So you can define an <tt>${maven.projectBasedir}/.mvn/extensions.xml</tt> file which looks like the following:</p>
+<p>The configuration for Apache Maven usage itself and projects built with resides in a number of places:</p><section>
+<h2><a name="MAVEN_OPTS_environment_variable:"></a>MAVEN_OPTS environment variable:</h2>
+<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to globally to Maven. E.g. JVM memory settings could be defined with the value -Xms256m -Xmx512m.</p></section><section>
+<h2><a name="settings.xml_file:"></a>settings.xml file:</h2>
+<p>Located in USER_HOME/.m2 the settings files is designed to contain any configuration for Maven usage across projects.</p></section><section>
+<h2><a name="a.mvn_folder:"></a>.mvn folder:</h2>
+<p>Located with in the projects top level folder, the files maven.config, jvm.config, and extensions.xml contain project specific configuration for running Maven.</p>
+<p>This folder is part of the project and may be checked in into your version control.</p><section>
+<h3><a name="a.mvn.2Fextensions.xml_file:"></a>.mvn/extensions.xml file:</h3>
+<p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you have other dependencies) which contains the extension and put it manually into the ${MAVEN_HOME}/lib/ext folder. This means you had to change the Maven installation. The consequence was that everyone who likes to use this needed to change it’s installation and makes the on-boarding for a developer much more inconvenient. The other option was to give the path to the jar on command line via mvn -Dmaven.ext.class.path=extension.jar. This has the drawback giving those options to your Maven build every time you are calling Maven. Not very convenient as well.</p>
+<p>From now on this can be done much more simpler and in a more Maven like way. So you can define an ${maven.projectBasedir}/.mvn/extensions.xml file which looks like the following:</p>
<div>
<div>
@@ -155,22 +151,19 @@
</extensions>
</pre></div></div>
-<p>Now you can simply use an extension by defining the usual maven coordinates groupId, artifactId, version as any other artifact. Furthermore all transitive dependencies of those extensions will automatically being downloaded from your repository. So no need to create a shaded artifact anymore.</p></div>
-<div class="section">
-<h3><a name="a.mvn.2Fmaven.config_file:"></a><tt>.mvn/maven.config</tt> file:</h3>
-<p>It’s really hard to define a general set of options for calling the maven command line. Starting with Maven 3.3.1+, this can be solved by putting this options to a script but this can now simple being done by defining <tt>${maven.projectBasedir}/.mvn/maven.config</tt> file which contains the configuration options for the <tt>mvn</tt> command line.</p>
-<p>For example things like <tt>-T3 -U --fail-at-end</tt>. So you only have to call Maven just by using <tt>mvn clean package</tt> instead of <tt>mvn -T3 -U --fail-at-end clean package</tt> and not to miss the <tt>-T3 -U --fail-at-end</tt> options on every call. The <tt>${maven.projectBasedir}/.mvn/maven.config</tt> is located in the <tt>${maven.projectBasedir}/.mvn/</tt> folder; also works if in the root of a multi module build.</p></div>
-<div class="section">
-<h3><a name="a.mvn.2Fjvm.config_file:"></a><tt>.mvn/jvm.config</tt> file:</h3>
-<p>Starting with Maven 3.3.1+ you can define JVM configuration via <tt>${maven.projectBasedir}/.mvn/jvm.config</tt> file which means you can define the options for your build on a per project base. This file will become part of your project and will be checked in along with your project. So no need anymore for <tt>MAVEN_OPTS</tt>, <tt>.mavenrc</tt> files. So for example if you put the following JVM options into the <tt>${maven.projectBasedir}/.mvn/jvm.config</tt> file</p>
+<p>Now you can simply use an extension by defining the usual maven coordinates groupId, artifactId, version as any other artifact. Furthermore all transitive dependencies of those extensions will automatically being downloaded from your repository. So no need to create a shaded artifact anymore.</p></section><section>
+<h3><a name="a.mvn.2Fmaven.config_file:"></a>.mvn/maven.config file:</h3>
+<p>It’s really hard to define a general set of options for calling the maven command line. Starting with Maven 3.3.1+, this can be solved by putting this options to a script but this can now simple being done by defining ${maven.projectBasedir}/.mvn/maven.config file which contains the configuration options for the mvn command line.</p>
+<p>For example things like -T3 -U --fail-at-end. So you only have to call Maven just by using mvn clean package instead of mvn -T3 -U --fail-at-end clean package and not to miss the -T3 -U --fail-at-end options on every call. The ${maven.projectBasedir}/.mvn/maven.config is located in the ${maven.projectBasedir}/.mvn/ folder; also works if in the root of a multi module build.</p></section><section>
+<h3><a name="a.mvn.2Fjvm.config_file:"></a>.mvn/jvm.config file:</h3>
+<p>Starting with Maven 3.3.1+ you can define JVM configuration via ${maven.projectBasedir}/.mvn/jvm.config file which means you can define the options for your build on a per project base. This file will become part of your project and will be checked in along with your project. So no need anymore for MAVEN_OPTS, .mavenrc files. So for example if you put the following JVM options into the ${maven.projectBasedir}/.mvn/jvm.config file</p>
<div>
<div>
<pre class="source"> -Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
</pre></div></div>
-<p>You don’t need to remember of using this options in <tt>MAVEN_OPTS</tt> or switching between different configurations. in the end, add the following:</p></div></div>
-<div class="section">
+<p>You don’t need to remember of using this options in MAVEN_OPTS or switching between different configurations. in the end, add the following:</p></section></section><section>
<h2><a name="Other_guides"></a>Other guides</h2>
<p>The following guides contain further information to specific configuration aspects:</p>
<ul>
@@ -182,7 +175,7 @@
<li><a href="./guides/mini/guide-mirror-settings.html">Configuring a repository mirror</a></li>
<li><a href="./guides/mini/guide-configuring-maven.html">Various Tips for Configuring Maven</a></li>
<li><a href="./guides/mini/guide-encryption.html">Password Encryption</a></li>
-</ul></div>
+</ul></section>
</div>
</div>
</div>
Modified: maven/website/content/continuous-integration.html
==============================================================================
--- maven/website/content/continuous-integration.html (original)
+++ maven/website/content/continuous-integration.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/continuous-integration.md at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/markdown/continuous-integration.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,9 +118,8 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
-<h2><a name="Continuous_Integration"></a>Continuous Integration</h2>
-<div class="section">
+<section>
+<h2><a name="Continuous_Integration"></a>Continuous Integration</h2><section>
<h3><a name="CI_Servers"></a>CI Servers</h3>
<p>Following is an alphabetical list of some CI servers we’ve heard mentioned around the Maven community:</p>
<ul>
@@ -133,7 +132,7 @@
<li><a class="externalLink" href="https://jenkins-ci.org/">Jenkins</a></li>
<li><a class="externalLink" href="https://www.jetbrains.com/teamcity/">TeamCity (JetBrains)</a></li>
<li><a class="externalLink" href="https://travis-ci.org/">Travis</a></li>
-</ul></div></div>
+</ul></section></section>
</div>
</div>
</div>
Modified: maven/website/content/developers/committer-environment.html
==============================================================================
--- maven/website/content/developers/committer-environment.html (original)
+++ maven/website/content/developers/committer-environment.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/developers/committer-environment.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/developers/committer-environment.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -120,27 +120,21 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Introduction"></a>Introduction</h2>
-<p>This document is intended to set up the Maven committer environment.</p></div>
-<div class="section">
+<p>This document is intended to set up the Maven committer environment.</p></section><section>
<h2><a name="Source_File_Encoding">Source File Encoding</a></h2>
-<p>When editing source files, make sure you use the right file encoding. For the Maven project, UTF-8 has been chosen as the default file encoding. UTF-8 is an encoding scheme for the Unicode character set and as such allows to encode all characters that Java can handle. The source files should not contain the byte order mark (BOM). There can be exceptions to this general rule, e.g. properties files are usually encoded using ISO-8859-1 as per the JRE API, so please keep this in mind, too.</p></div>
-<div class="section">
+<p>When editing source files, make sure you use the right file encoding. For the Maven project, UTF-8 has been chosen as the default file encoding. UTF-8 is an encoding scheme for the Unicode character set and as such allows to encode all characters that Java can handle. The source files should not contain the byte order mark (BOM). There can be exceptions to this general rule, e.g. properties files are usually encoded using ISO-8859-1 as per the JRE API, so please keep this in mind, too.</p></section><section>
<h2><a name="Subversion_Configuration"></a>Subversion Configuration</h2>
-<p>Before committing files in subversion repository, you need to read the <a class="externalLink" href="https://www.apache.org/dev/version-control.html#https-svn">Committer Subversion Access</a> document and you must set your svn client with this properties file: <a href="./svn-eol-style.txt">svn-eol-style.txt</a></p></div>
-<div class="section">
+<p>Before committing files in subversion repository, you need to read the <a class="externalLink" href="https://www.apache.org/dev/version-control.html#https-svn">Committer Subversion Access</a> document and you must set your svn client with this properties file: <a href="./svn-eol-style.txt">svn-eol-style.txt</a></p></section><section>
<h2><a name="Maven_Code_Style">Maven Code Style</a></h2>
-<p>The following sections show how to set up the code style for Maven in IDEA and Eclipse. It is strongly preferred that patches use this style before they are supplied.</p>
-<div class="section">
+<p>The following sections show how to set up the code style for Maven in IDEA and Eclipse. It is strongly preferred that patches use this style before they are supplied.</p><section>
<h3><a name="IntelliJ_IDEA_4.5.2B"></a>IntelliJ IDEA 4.5+</h3>
-<p>Download <tt><a href="./maven-idea-codestyle.xml">maven-idea-codestyle.xml</a></tt> and copy it to <tt>~~/Library/Preferences/IntelliJIdeaxx/codestyles</tt> then restart IDEA (with xx your idea version). On Windows, try <tt>C:\Documents and Settings\<username>\.IntelliJIDEA\config\codestyles</tt></p>
-<p>After this, restart IDEA and open the settings to select the new code style.</p></div>
-<div class="section">
+<p>Download <code><a href="./maven-idea-codestyle.xml">maven-idea-codestyle.xml</a></code> and copy it to <code>~~/Library/Preferences/IntelliJIdeaxx/codestyles</code> then restart IDEA (with xx your idea version). On Windows, try <code>C:\Documents and Settings\<username>\.IntelliJIDEA\config\codestyles</code></p>
+<p>After this, restart IDEA and open the settings to select the new code style.</p></section><section>
<h3><a name="Eclipse_3.2.2B"></a>Eclipse 3.2+</h3>
-<p>Download <tt><a href="./maven-eclipse-codestyle.xml">maven-eclipse-codestyle.xml</a></tt>.</p>
-<p>After this, select Window > Preferences, and open up the configuration for Java > Code Style > Code Formatter. Click on the button labeled Import... and select the file you downloaded. Give the style a name, and click OK.</p></div></div>
-<div class="section">
+<p>Download <code><a href="./maven-eclipse-codestyle.xml">maven-eclipse-codestyle.xml</a></code>.</p>
+<p>After this, select Window > Preferences, and open up the configuration for Java > Code Style > Code Formatter. Click on the button labeled Import... and select the file you downloaded. Give the style a name, and click OK.</p></section></section><section>
<h2><a name="Setting_up_SSH_public.2Fprivate_keys"></a>Setting up SSH public/private keys</h2>
<p>By default, SSH (Secure Shell) asks you to enter your password each time, i.e.:</p>
<div class="source"><pre class="prettyprint linenums">>ssh YOUR_APACHE_USERNAME@people.apache.org
@@ -155,9 +149,9 @@ Your identification has been saved in YO
Your public key has been saved in YOUR_APACHE_USERNAME@apache.org.pub.
The key fingerprint is:
0c:16:c7:44:9e:a6:2c:c0:8a:87:04:07:a0:5b:94:d2 YOUR_APACHE_USERNAME@apache.org</pre></div>
-<p>Then, paste the content of the local <tt>~/.ssh/YOUR_APACHE_USERNAME.pub</tt> file into the file <tt>/home/YOUR_APACHE_USERNAME/.ssh/authorized_keys</tt> on the Apache remote host.</p>
-<p><b>Note</b>: under Cygwin, it is located at <tt>{cygwin.install.path}\home\YOUR_MACHINE_USERNAME\.ssh</tt>. You need to copy the content of <tt>{cygwin.install.path}\home\YOUR_MACHINE_USERNAME\.ssh</tt> into <tt>C:\Documents and Settings\YOUR_MACHINE_USERNAME\.ssh</tt> for Maven.</p>
-<p>You also need to modify the <tt>~/.ssh/config</tt> to use this identity file when communicating with *.apache.org</p>
+<p>Then, paste the content of the local <code>~/.ssh/YOUR_APACHE_USERNAME.pub</code> file into the file <code>/home/YOUR_APACHE_USERNAME/.ssh/authorized_keys</code> on the Apache remote host.</p>
+<p><b>Note</b>: under Cygwin, it is located at <code>{cygwin.install.path}\home\YOUR_MACHINE_USERNAME\.ssh</code>. You need to copy the content of <code>{cygwin.install.path}\home\YOUR_MACHINE_USERNAME\.ssh</code> into <code>C:\Documents and Settings\YOUR_MACHINE_USERNAME\.ssh</code> for Maven.</p>
+<p>You also need to modify the <code>~/.ssh/config</code> to use this identity file when communicating with *.apache.org</p>
<div class="source"><pre class="prettyprint linenums">Host *.apache.org
User=YOUR_APACHE_USERNAME
IdentityFile=~/.ssh/YOUR_APACHE_USERNAME@apache.org</pre></div>
@@ -170,15 +164,14 @@ FreeBSD 8.2-RELEASE-p4 (GENERIC) #1 r226
This is minotaur.apache.org (a.k.a. people.apache.org).
...
-YOUR_APACHE_USERNAME@minotaur:~$</pre></div></div>
-<div class="section">
+YOUR_APACHE_USERNAME@minotaur:~$</pre></div></section><section>
<h2><a name="Useful_software"></a>Useful software</h2>
<p>The Maven Team uses several software. Here is a partial list:</p>
<ul>
<li><a class="externalLink" href="http://www.cygwin.com/">Cygwin</a>: collection of free software tools to allow various versions of Microsoft Windows to act somewhat like a Unix system</li>
<li><a class="externalLink" href="http://winscp.net/">WinSCP</a>: SFTP client for Windows.</li>
<li><a class="externalLink" href="http://tortoisesvn.tigris.org/">TortoiseSVN</a>: Subversion client, implemented as a Windows shell extension.</li>
-<li><a class="externalLink" href="http://www.gnupg.org/">GnuPG</a>: GNU Privacy Guard.</li></ul></div>
+<li><a class="externalLink" href="http://www.gnupg.org/">GnuPG</a>: GNU Privacy Guard.</li></ul></section>
</div>
</div>
</div>
Modified: maven/website/content/developers/committer-settings.html
==============================================================================
--- maven/website/content/developers/committer-settings.html (original)
+++ maven/website/content/developers/committer-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/developers/committer-settings.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/developers/committer-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">
@@ -121,10 +121,9 @@ Dennis Lundberg" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Introduction"></a>Introduction</h2>
-<p>This document is intended to set up the Maven committer settings, i.e. the <tt>${user.home}/.m2/settings.xml</tt>.</p>
-<div class="section">
+<p>This document is intended to set up the Maven committer settings, i.e. the <code>${user.home}/.m2/settings.xml</code>.</p><section>
<h3><a name="Enable_Apache_Servers"></a>Enable Apache Servers</h3>
<p>Maven uses several servers configuration to deploy snapshots, releases and documentation on the Apache servers. You need to tell to Maven what your Apache username is. Please note that the servers now use your LDAP credentials, which may differ from your old SVN credentials.</p>
<p><b>It is highly recommended to use Maven's <a href="../guides/mini/guide-encryption.html"> password encryption capabilities</a> for your passwords</b>.</p>
@@ -165,10 +164,9 @@ Dennis Lundberg" />
...
</servers>
</settings></pre></div>
-<p>You also need to be a member of the group <tt>apcvs</tt> and <tt>maven</tt> on <tt>people.apache.org</tt>.</p></div>
-<div class="section">
+<p>You also need to be a member of the group <code>apcvs</code> and <code>maven</code> on <code>people.apache.org</code>.</p></section><section>
<h3><a name="Enable_sending_announcement_e-mails"></a>Enable sending announcement e-mails</h3>
-<p>To be able to send out announcements of Maven releases you need to add a couple of properties to the <tt>apache-release</tt> profile.</p>
+<p>To be able to send out announcements of Maven releases you need to add a couple of properties to the <code>apache-release</code> profile.</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
<profiles>
@@ -181,7 +179,7 @@ Dennis Lundberg" />
</profile>
...
</profiles>
-</settings></pre></div></div></div>
+</settings></pre></div></section></section>
</div>
</div>
</div>
Modified: maven/website/content/developers/conventions/code.html
==============================================================================
--- maven/website/content/developers/conventions/code.html (original)
+++ maven/website/content/developers/conventions/code.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/developers/conventions/code.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/developers/conventions/code.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">
@@ -130,10 +130,9 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Maven_Code_Style_And_Code_Conventions"></a>Maven Code Style And Code Conventions</h2>
-<p>This document describes how developers and contributors should write code. The reasoning of these styles and conventions is mainly for consistency, readability and maintainability reasons.</p>
-<div class="section">
+<p>This document describes how developers and contributors should write code. The reasoning of these styles and conventions is mainly for consistency, readability and maintainability reasons.</p><section>
<h3><a name="Generic_Code_Style_And_Convention"></a>Generic Code Style And Convention</h3>
<p>All working files (java, xml, others) should respect the following conventions:</p>
<ul>
@@ -143,14 +142,12 @@
<ul>
<li><b>Indentation</b>: <b>Never</b> use tabs!</li>
<li><b>Line wrapping</b>: Always use a 120-column line width.</li></ul>
-<p><b>Note</b>: The specific styles and conventions, listed in the next sections, could override these generic rules.</p></div>
-<div class="section">
-<h3><a name="Java">Java</a></h3>
-<div class="section">
+<p><b>Note</b>: The specific styles and conventions, listed in the next sections, could override these generic rules.</p></section><section>
+<h3><a name="Java">Java</a></h3><section>
<h4><a name="Java_Code_Style">Java Code Style</a></h4>
<p>The Maven style for Java is mainly:</p>
<ul>
-<li><b>White space</b>: One space after control statements and between arguments (i.e. <tt>if ( foo )</tt> instead of <tt>if(foo)</tt>), <tt>myFunc( foo, bar, baz )</tt> instead of <tt>myFunc(foo,bar,baz)</tt>). No spaces after methods names (i.e. <tt>void myMethod(), myMethod( "foo" )</tt>)</li>
+<li><b>White space</b>: One space after control statements and between arguments (i.e. <code>if ( foo )</code> instead of <code>if(foo)</code>), <code>myFunc( foo, bar, baz )</code> instead of <code>myFunc(foo,bar,baz)</code>). No spaces after methods names (i.e. <code>void myMethod(), myMethod( "foo" )</code>)</li>
<li><b>Indentation</b>: Always use 4 space indents and <b>never</b> use tabs!</li>
<li><b>Blocks</b>: Always enclose with a new line brace.</li>
<li><b>Line wrapping</b>: Always use a 120-column line width for Java code and Javadoc.</li>
@@ -217,16 +214,13 @@
// ----------------------------------------------------------------------
...
}</pre></div></li></ul>
-<p>The following sections show how to set up the code style for Maven in IDEA and Eclipse. It is strongly preferred that patches use this style before they are applied.</p>
-<div class="section">
+<p>The following sections show how to set up the code style for Maven in IDEA and Eclipse. It is strongly preferred that patches use this style before they are applied.</p><section>
<h5><a name="IntelliJ_IDEA_4.5.2B"></a>IntelliJ IDEA 4.5+</h5>
-<p>Download <tt><a href="../../developers/maven-idea-codestyle.xml">maven-idea-codestyle.xml</a></tt> and copy it to <tt>~/.IntelliJIDEA/config/codestyles</tt> then restart IDEA. On Windows, try <tt>C:\Documents and Settings<username>\.IntelliJIDEA\config\codestyles</tt></p>
-<p>After this, restart IDEA and open the settings to select the new code style.</p></div>
-<div class="section">
+<p>Download <code><a href="../../developers/maven-idea-codestyle.xml">maven-idea-codestyle.xml</a></code> and copy it to <code>~/.IntelliJIDEA/config/codestyles</code> then restart IDEA. On Windows, try <code>C:\Documents and Settings<username>\.IntelliJIDEA\config\codestyles</code></p>
+<p>After this, restart IDEA and open the settings to select the new code style.</p></section><section>
<h5><a name="Eclipse_3.2.2B"></a>Eclipse 3.2+</h5>
-<p>Download <tt><a href="../../developers/maven-eclipse-codestyle.xml">maven-eclipse-codestyle.xml</a></tt>.</p>
-<p>After this, select Window > Preferences, and open up the configuration for Java > Code Style > Code Formatter. Click on the button labeled Import... and select the file you downloaded. Give the style a name, and click OK.</p></div></div>
-<div class="section">
+<p>Download <code><a href="../../developers/maven-eclipse-codestyle.xml">maven-eclipse-codestyle.xml</a></code>.</p>
+<p>After this, select Window > Preferences, and open up the configuration for Java > Code Style > Code Formatter. Click on the button labeled Import... and select the file you downloaded. Give the style a name, and click OK.</p></section></section><section>
<h4><a name="Java_Code_Convention">Java Code Convention</a></h4>
<p>For consistency reasons, our Java code convention is mainly:</p>
<ul>
@@ -235,13 +229,10 @@
<li><b>Modifier</b>: Avoid using final modifier on all member variables and arguments. Prefer using private or protected member instead of public member.</li>
<li><b>Exceptions</b>: Throw meaningful exceptions to makes debugging and testing more easy.</li>
<li><b>Documentation</b>: Document public interfaces well, i.e. all non-trivial public and protected functions should include Javadoc that indicates what it does. <b>Note</b>: it is an ongoing convention for the Maven Team.</li>
-<li><b>Testing</b>: All non-trivial public classes should include corresponding unit or IT tests.</li></ul></div>
-<div class="section">
+<li><b>Testing</b>: All non-trivial public classes should include corresponding unit or IT tests.</li></ul></section><section>
<h4><a name="JavaDoc_Convention">JavaDoc Convention</a></h4>
-<p>TO BE DISCUSSED</p></div></div>
-<div class="section">
-<h3><a name="XML">XML</a></h3>
-<div class="section">
+<p>TO BE DISCUSSED</p></section></section><section>
+<h3><a name="XML">XML</a></h3><section>
<h4><a name="XML_Code_Style">XML Code Style</a></h4>
<p>The Maven style for XML files is mainly:</p>
<ul>
@@ -259,11 +250,9 @@
<p>or</p>
<div class="source"><pre class="prettyprint linenums"> <!-- ====================================================================== -->
<!-- Block documentation -->
- <!-- ====================================================================== --></pre></div></li></ul></div>
-<div class="section">
+ <!-- ====================================================================== --></pre></div></li></ul></section><section>
<h4><a name="Generic_XML_Code_Convention">Generic XML Code Convention</a></h4>
-<p>No generic code convention exists yet for XML files.</p></div>
-<div class="section">
+<p>No generic code convention exists yet for XML files.</p></section><section>
<h4><a name="POM_Code_Convention">POM Code Convention</a></h4>
<p>The team has <a class="externalLink" href="https://maven.40175.n5.nabble.com/Proposal-Pom-Code-Style-WAS-svn-commit-r670264-maven-plugins-trunk-maven-site-plugin-pom-xml-td210642.html#a210643">voted</a> during the end of June 2008 to follow a specific POM convention to ordering POM elements. The consequence of this vote is that the <a class="externalLink" href="https://maven.apache.org/ref/current/maven-model/maven.html">Maven project descriptor</a> is <b>no more</b> considered as the reference for the ordering.</p>
<p>The following is the recommended ordering for all Maven POM files:</p>
@@ -316,19 +305,17 @@
<ol style="list-style-type: decimal">
<li>The <project/> element is always on one line.</li>
<li>The blocks are voluntary separated by a new line to improve the readingness.</li>
-<li>The dependencies in <dependencies/> and <dependencyManagement/> tags have no specific ordering. Developers are free to choose the ordering, but grouping dependencies by topics (like groupId i.e. <tt>org.apache.maven</tt>) is a good practice.</li></ol>
-<p><b>Note</b>: There existing two alternativs to change order of a pom file <a class="externalLink" href="https://www.mojohaus.org/tidy-maven-plugin/">Tidy Maven Plugin</a> or the <a class="externalLink" href="https://github.com/Ekryd/sortpom">Sortpom Maven Plugin</a>.</p></div>
-<div class="section">
+<li>The dependencies in <dependencies/> and <dependencyManagement/> tags have no specific ordering. Developers are free to choose the ordering, but grouping dependencies by topics (like groupId i.e. <code>org.apache.maven</code>) is a good practice.</li></ol>
+<p><b>Note</b>: There existing two alternativs to change order of a pom file <a class="externalLink" href="https://www.mojohaus.org/tidy-maven-plugin/">Tidy Maven Plugin</a> or the <a class="externalLink" href="https://github.com/Ekryd/sortpom">Sortpom Maven Plugin</a>.</p></section><section>
<h4><a name="XDOC_Code_Convention">XDOC Code Convention</a></h4>
<p>For consistency and readability reasons, XDOC files should respect:</p>
<ul>
<li><b>Metadata</b>: Always specify metadata in the <properties/> tag.</li>
-<li><b>Sections</b>: Always use a new line with indentation for <section/> tags.</li></ul></div>
-<div class="section">
+<li><b>Sections</b>: Always use a new line with indentation for <section/> tags.</li></ul></section><section>
<h4><a name="FML_Code_Convention">FML Code Convention</a></h4>
<p>For readability reasons, FML files should respect:</p>
<ul>
-<li><b>FAQ</b>: Always use a new line with indentation for <faq/> tags.</li></ul></div></div></div>
+<li><b>FAQ</b>: Always use a new line with indentation for <faq/> tags.</li></ul></section></section></section>
</div>
</div>
</div>
Modified: maven/website/content/developers/conventions/git.html
==============================================================================
--- maven/website/content/developers/conventions/git.html (original)
+++ maven/website/content/developers/conventions/git.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/developers/conventions/git.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/developers/conventions/git.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">
@@ -130,29 +130,24 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Maven_Git_Convention"></a>Maven Git Convention</h2>
-<p>This document describes how developers should use Git. The Maven project is in the process of migrating some of its components from svn to git.</p>
-<div class="section">
+<p>This document describes how developers should use Git. The Maven project is in the process of migrating some of its components from svn to git.</p><section>
<h3><a name="Git_migration"></a>Git migration</h3>
-<p>Information on the migration is here: <a class="externalLink" href="https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration">https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration</a></p></div>
-<div class="section">
-<h3><a name="Git_Configuration"></a>Git Configuration</h3>
-<div class="section">
+<p>Information on the migration is here: <a class="externalLink" href="https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration">https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration</a></p></section><section>
+<h3><a name="Git_Configuration"></a>Git Configuration</h3><section>
<h4><a name="For_contributors_who_are_not_committers"></a>For contributors who are not committers</h4>
<p>Apache git repositories are at <i> <<git://git.apache.org</i>>>. However, the ASF uses clones on github.com to make it easier for people to contribute changes via pull requests.</p>
<p>To contribute to a Maven component that is maintained in git, please follow these steps:</p>
<ol style="list-style-type: decimal">
<li>create a JIRA for bug or improvement that you wish to work on. The Maven project uses JIRA to organize and track our work, and in particular to keep track of which changes are included in which releases.</li>
-<li>Make a fork of the official ASF clone from github.com. For example, <tt>https://github.com/apache/maven-scm</tt>.</li>
+<li>Make a fork of the official ASF clone from github.com. For example, <code>https://github.com/apache/maven-scm</code>.</li>
<li>Make a branch named after your JIRA. This is not <i>required</i>, but it makes it easier for Maven committers to keep track of your contribution.</li>
<li>Make your changes. As always, unit or integration tests make it much easier for us to accept your changes.</li>
<li>Make a pull request to pull your changes to the official clone. Add a link to your pull request to the JIRA. Committers will take it from here.</li>
-<li></li></ol></div>
-<div class="section">
+<li></li></ol></section><section>
<h4><a name="For_committers"></a>For committers</h4>
-<p>Committers may, of course, commit directly to the ASF repositories. For complex changes, you may find it valuable to make a pull request at github to make it easier to collaborate with others.</p>
-<div class="section">
+<p>Committers may, of course, commit directly to the ASF repositories. For complex changes, you may find it valuable to make a pull request at github to make it easier to collaborate with others.</p><section>
<h5><a name="Commit_Message_Template">Commit Message Template</a></h5>
<p>Commits should be focused on one issue at a time, because that makes it easier for others to review the commit.</p>
<p>A commit message should use this template:</p>
@@ -164,26 +159,21 @@ o Comments</pre></div>
<ul>
<li><b>ISSUE-1</b> can be omitted if there was no relevant JIRA issue, though you are strongly encouraged to create one for significant changes.</li>
<li><b>Submitted by</b> only needs to be specified when a patch is being applied for a non-committer.</li>
-<li><b>Comments</b> some optional words about the solution.</li></ul></div></div></div></div>
-<div class="section">
+<li><b>Comments</b> some optional words about the solution.</li></ul></section></section></section></section><section>
<h2><a name="eg:"></a>eg:</h2>
<div class="source"><pre class="prettyprint linenums">[MNG-1456] Added the foo to the bar
Submitted by: Baz Bazman
-o Applied without change</pre></div>
-<div class="section">
+o Applied without change</pre></div><section>
<h3><a name="Apply_User_Patch"></a>Apply User Patch</h3>
<p>To keep the history of contributions clear, The committer should usually apply the patch without any <b>major</b> modifications, and then create his or her own commits for further modifications. However, committers should never commit code to a live branch which is not suitable to release. If a contribution requires significant work to make it useful, commit it to a branch, fix it up, and merge the branch.</p>
<p>If the user created a pull request, the committer is responsible for closing that pull request. You do this by adding a note to a commit message:</p>
<div class="source"><pre class="prettyprint linenums"> Closes #NNN.</pre></div>
-<p>where NNN is the number of the pull request.</p></div>
-<div class="section">
-<h3><a name="Edit_Commit_Message"></a>Edit Commit Message</h3></div></div>
-<div class="section">
+<p>where NNN is the number of the pull request.</p></section><section>
+<h3><a name="Edit_Commit_Message"></a>Edit Commit Message</h3></section></section><section>
<h2><a name="to_edit_last_commit_comment:"></a>to edit last commit comment:</h2>
<div>
-<pre>$ git commit --amend -m "new comment"</pre></div>
-<div class="section">
+<pre>$ git commit --amend -m "new comment"</pre></div><section>
<h3><a name="Workflow"></a>Workflow</h3>
<p>Workflow for svn folks is something like :</p>
<div>
@@ -204,14 +194,12 @@ $ git fetch
// this moves 'origin/master'
$ git rebase origin/master
// this reapplies your local changes on top of origin/master
-$ git push</pre></div></div>
-<div class="section">
+$ git push</pre></div></section><section>
<h3><a name="Other_useful_Git_commands_while_developing"></a>Other useful Git commands while developing</h3>
<p>If you've done a chunk of work and you would like to ditch your changes and start from scratch use this command to revert to the original checkout:</p>
<div>
<pre>$ git checkout .</pre></div>
-<p>TODO .gitignore</p>
-<div class="section">
+<p>TODO .gitignore</p><section>
<h4><a name="power-git_checkout"></a>power-git checkout</h4>
<p>This checkout is typical for highly experienced git users, and may serve as inspiration for others; as usual the best way to learn is by doing. Sample shown for maven-surefire</p>
<p>Go to https://github.com/apache/maven-surefire and fork surefire to your own github account.</p>
@@ -242,7 +230,7 @@ git push apache # upload to apache</pre>
<pre>
git checkout pr/10
git rebase apache/master
-git push apache</pre></div></div></div></div>
+git push apache</pre></div></section></section></section>
</div>
</div>
</div>
Modified: maven/website/content/developers/conventions/jira.html
==============================================================================
--- maven/website/content/developers/conventions/jira.html (original)
+++ maven/website/content/developers/conventions/jira.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/developers/conventions/jira.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/developers/conventions/jira.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">
@@ -130,46 +130,37 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Maven_JIRA_Convention"></a>Maven JIRA Convention</h2>
-<p>This document describes how Maven developers should use JIRA, our issue management system.</p>
-<div class="section">
+<p>This document describes how Maven developers should use JIRA, our issue management system.</p><section>
<h3><a name="When_To_Create_a_JIRA_Issue.3F"></a>When To Create a JIRA Issue?</h3>
<p>This section discusses when to create a JIRA issue versus just committing a change in Git (eventually through a PR).</p>
<ul>
<li><b>Minor changes</b>, like code reformatting, documentation fixes, etc. that aren't going to impact other users can be committed without much issue.</li>
-<li><b>Larger changes</b>, like bug fixes, API changes, significant refactoring, new classes, and pretty much any change of more than 100 lines, should have a JIRA ticket associated with it, or at least an email discussion.<br />Creating a JIRA issue and referring it in commit comment will ease tracking what changes happen in a release, using JIRA automatic release notes creation.</li></ul></div>
-<div class="section">
+<li><b>Larger changes</b>, like bug fixes, API changes, significant refactoring, new classes, and pretty much any change of more than 100 lines, should have a JIRA ticket associated with it, or at least an email discussion.<br />Creating a JIRA issue and referring it in commit comment will ease tracking what changes happen in a release, using JIRA automatic release notes creation.</li></ul></section><section>
<h3><a name="How_To_Use_Issue_Details.3F"></a>How To Use Issue Details?</h3>
-<p>This section presents some conventions about the issue fields.</p>
-<div class="section">
+<p>This section presents some conventions about the issue fields.</p><section>
<h4><a name="Priority"></a>Priority</h4>
<p>Committers has the responsibility to realign priority by editing the issue.</p>
-<p><b>Reasoning</b>: having a correct release note.</p></div>
-<div class="section">
+<p><b>Reasoning</b>: having a correct release note.</p></section><section>
<h4><a name="Assignee"></a>Assignee</h4>
-<p>Committers could assign an issue to a specific committer if he thinks it is the right committer.</p></div>
-<div class="section">
+<p>Committers could assign an issue to a specific committer if he thinks it is the right committer.</p></section><section>
<h4><a name="Component.2Fs"></a>Component/s</h4>
<p>Committers has the responsibility to specify the correct the component by editing the issue.</p>
-<p><b>Reasoning</b>: having a correct release note.</p></div>
-<div class="section">
+<p><b>Reasoning</b>: having a correct release note.</p></section><section>
<h4><a name="Affects_Version.2Fs"></a>Affects Version/s</h4>
<p>By default, the Maven team considers that an issue, which affects a given version, affects also precedent versions, i.e. issue which affects Maven 2.0.9 will affect also 2.0, 2.0.1 ... 2.0.9. If it is a regression, the committers should specify the affected versions.</p>
-<p><b>Reasoning</b>: having a correct release note.</p></div>
-<div class="section">
+<p><b>Reasoning</b>: having a correct release note.</p></section><section>
<h4><a name="Fix_Version.2Fs"></a>Fix Version/s</h4>
-<p>TO BE DISCUSSED</p></div>
-<div class="section">
+<p>TO BE DISCUSSED</p></section><section>
<h4><a name="Time_Tracking"></a>Time Tracking</h4>
-<p>The Maven team never uses it. Committers could do it, but like said, it will never be used.</p></div></div>
-<div class="section">
+<p>The Maven team never uses it. Committers could do it, but like said, it will never be used.</p></section></section><section>
<h3><a name="Further_Links"></a>Further Links</h3>
<ul>
<li><a class="externalLink" href="https://www.atlassian.com/software/jira/docs/latest/">JIRA Documentation</a></li>
<li><a class="externalLink" href="https://www.atlassian.com/software/jira/docs/latest/issues.html">What is an Issue?</a></li>
<li><a class="externalLink" href="https://www.atlassian.com/software/jira/docs/latest/projects.html">What is a project?</a></li>
-<li><a class="externalLink" href="https://markmail.org/message/wfv2lw66i2gggnaq">how we handle JIRA versions Thread</a></li></ul></div></div>
+<li><a class="externalLink" href="https://markmail.org/message/wfv2lw66i2gggnaq">how we handle JIRA versions Thread</a></li></ul></section></section>
</div>
</div>
</div>