Modified: maven/website/content/articles.html ============================================================================== --- maven/website/content/articles.html (original) +++ maven/website/content/articles.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/xdoc/articles.xml at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/xdoc/articles.xml at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Brett Porter" /> <meta name="author" content="Vincent Massol" /> <title>Maven – External Resources on Maven</title> @@ -126,49 +126,49 @@ <section> -<h2><a name="Books_on_Maven"></a>Books on Maven</h2> +<h1><a name="Books_on_Maven"></a>Books on Maven</h1> <div style="float: left; margin-right: 5em;"> -<a class="externalLink" href="https://www.packtpub.com/application-development/apache-maven-cookbook";><img src="images/books/apache_maven_cookbook.jpg" title="Apache Maven 3.0 Cookbook" alt="" /></a> +<a href="https://www.packtpub.com/application-development/apache-maven-cookbook"; class="externalLink"><img src="images/books/apache_maven_cookbook.jpg" title="Apache Maven 3.0 Cookbook" alt="" /></a> </div> <div style="min-height: 220px"> -<p><a class="externalLink" href="https://www.packtpub.com/application-development/apache-maven-cookbook";><b>Apache Maven Cookbook</b></a></p> +<p><a href="https://www.packtpub.com/application-development/apache-maven-cookbook"; class="externalLink"><strong>Apache Maven Cookbook</strong></a></p> <ul> -<li><b>Covers: </b>Maven 3</li> +<li><strong>Covers: </strong>Maven 3</li> -<li><b>Published: </b> Packt Publishing (August 2015)</li> +<li><strong>Published: </strong> Packt Publishing (August 2015)</li> -<li><b>Authors: </b> Raghuram Bharathan</li> +<li><strong>Authors: </strong> Raghuram Bharathan</li> -<li><b>Buy the Book:</b> <a class="externalLink" href="https://www.packtpub.com/application-development/apache-maven-cookbook";>Packt</a>, <a class="externalLink" href="https://www.amazon.com/Apache-Maven-Cookbook-Raghuram-Bharathan/dp/1785286129/ref=sr_1_1";>Amazon</a></li> +<li><strong>Buy the Book:</strong> <a href="https://www.packtpub.com/application-development/apache-maven-cookbook"; class="externalLink">Packt</a>, <a href="https://www.amazon.com/Apache-Maven-Cookbook-Raghuram-Bharathan/dp/1785286129/ref=sr_1_1"; class="externalLink">Amazon</a></li> </ul> </div> <div style="float: left; margin-right: 5em;"> -<a class="externalLink" href="https://www.packtpub.com/apache-maven-3-0-cookbook/book";><img src="images/books/apache_maven_3_0_cookbook.jpg" title="Apache Maven 3.0 Cookbook" alt="" /></a> +<a href="https://www.packtpub.com/apache-maven-3-0-cookbook/book"; class="externalLink"><img src="images/books/apache_maven_3_0_cookbook.jpg" title="Apache Maven 3.0 Cookbook" alt="" /></a> </div> <div style="min-height: 220px"> -<p><a class="externalLink" href="https://www.packtpub.com/apache-maven-3-0-cookbook/book";><b>Apache Maven 3.0 Cookbook</b></a></p> +<p><a href="https://www.packtpub.com/apache-maven-3-0-cookbook/book"; class="externalLink"><strong>Apache Maven 3.0 Cookbook</strong></a></p> <ul> -<li><b>Covers: </b>Maven 3</li> +<li><strong>Covers: </strong>Maven 3</li> -<li><b>Published: </b> Packt Publishing (August 2011)</li> +<li><strong>Published: </strong> Packt Publishing (August 2011)</li> -<li><b>Authors: </b> Srirangan</li> +<li><strong>Authors: </strong> Srirangan</li> -<li><b>Buy the Book:</b> <a class="externalLink" href="https://www.packtpub.com/apache-maven-3-0-cookbook/book";>Packt</a>, <a class="externalLink" href="https://www.amazon.com/Apache-Maven-3-Cookbook-Srirangan/dp/1849512442/ref=sr_1_1?ie=UTF8&qid=1315861966&sr=8-1";>Amazon</a></li> +<li><strong>Buy the Book:</strong> <a href="https://www.packtpub.com/apache-maven-3-0-cookbook/book"; class="externalLink">Packt</a>, <a href="https://www.amazon.com/Apache-Maven-3-Cookbook-Srirangan/dp/1849512442/ref=sr_1_1?ie=UTF8&qid=1315861966&sr=8-1"; class="externalLink">Amazon</a></li> </ul> </div> @@ -178,30 +178,30 @@ </div> <div style="float: left; margin-right: 5em;"> -<a class="externalLink" href="https://www.packtpub.com/getting-started-with-apache-maven/video";></a> +<a href="https://www.packtpub.com/getting-started-with-apache-maven/video"; class="externalLink"></a> </div> <div style="min-height: 220px"> -<p><a class="externalLink" href="https://www.packtpub.com/getting-started-with-apache-maven/video";><b>Getting Started with Apache Maven [Video]</b></a></p> +<p><a href="https://www.packtpub.com/getting-started-with-apache-maven/video"; class="externalLink"><strong>Getting Started with Apache Maven [Video]</strong></a></p> <ul> -<li><b>Covers: </b>Maven 2.2.1, and above</li> +<li><strong>Covers: </strong>Maven 2.2.1, and above</li> -<li><b>Published: </b> Packt Publishing (September 30, 2013)</li> +<li><strong>Published: </strong> Packt Publishing (September 30, 2013)</li> -<li><b>Authors: </b>Russell Gold +<li><strong>Authors: </strong>Russell Gold </li> -<li><b>Buy the Video:</b> <a class="externalLink" href="https://www.packtpub.com/getting-started-with-apache-maven/video";>Packt</a></li> +<li><strong>Buy the Video:</strong> <a href="https://www.packtpub.com/getting-started-with-apache-maven/video"; class="externalLink">Packt</a></li> </ul> </div> </section> <section> -<h2><a name="Articles_on_Maven"></a>Articles on Maven</h2> +<h1><a name="Articles_on_Maven"></a>Articles on Maven</h1> <p> If you are writing an article on Maven we suggest contacting the developers on the mailing list as we would be happy @@ -227,9 +227,9 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="https://www.javaadvent.com/2021/12/from-maven-3-to-maven-5.html";>From Maven 3 to Maven 5</a></td> +<td align="left"><a href="https://www.javaadvent.com/2021/12/from-maven-3-to-maven-5.html"; class="externalLink">From Maven 3 to Maven 5</a></td> -<td><a class="externalLink" href="https://www.javaadvent.com/";>JVM Advent</a></td> +<td><a href="https://www.javaadvent.com/"; class="externalLink">JVM Advent</a></td> <td>Hervé Boutemy</td> @@ -238,7 +238,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="https://maarten.mulders.it/2021/03/introduction-to-maven-toolchains/";>Introduction to Maven Toolchains</a></td> +<td align="left"><a href="https://maarten.mulders.it/2021/03/introduction-to-maven-toolchains/"; class="externalLink">Introduction to Maven Toolchains</a></td> <td></td> @@ -249,7 +249,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="https://maarten.mulders.it/2020/11/whats-new-in-maven-4/";>What's New in Maven 4</a></td> +<td align="left"><a href="https://maarten.mulders.it/2020/11/whats-new-in-maven-4/"; class="externalLink">What's New in Maven 4</a></td> <td></td> @@ -260,7 +260,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="https://maarten.mulders.it/2020/01/customise-the-maven-release-process/";>Customise the Maven Release process</a></td> +<td align="left"><a href="https://maarten.mulders.it/2020/01/customise-the-maven-release-process/"; class="externalLink">Customise the Maven Release process</a></td> <td></td> @@ -271,7 +271,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/";>Create a Customized Build Process in Maven</a></td> +<td align="left"><a href="http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/"; class="externalLink">Create a Customized Build Process in Maven</a></td> <td></td> @@ -282,7 +282,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="http://www.manuelrecena.com/docs/maven_090625.pdf";>Maven: mas que una herramienta de construccion (in Spanish)</a></td> +<td align="left"><a href="http://www.manuelrecena.com/docs/maven_090625.pdf"; class="externalLink">Maven: mas que una herramienta de construccion (in Spanish)</a></td> <td></td> @@ -293,7 +293,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="http://www.theserverside.com/tt/articles/article.tss?l=Introductiontom2eclipse";>Introduction to m2eclipse</a></td> +<td align="left"><a href="http://www.theserverside.com/tt/articles/article.tss?l=Introductiontom2eclipse"; class="externalLink">Introduction to m2eclipse</a></td> <td>TheServerSide</td> @@ -304,7 +304,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="http://msaitozen.googlepages.com/maven2.x_dokuman.pdf";>Maven 2.x (in Turkish)</a></td> +<td align="left"><a href="http://msaitozen.googlepages.com/maven2.x_dokuman.pdf"; class="externalLink">Maven 2.x (in Turkish)</a></td> <td>Anadolu Üniversitesi</td> @@ -315,7 +315,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="http://www.theserverside.com/tt/articles/article.tss?l=SettingUpMavenRepository";>Setting up the Internal Repository</a></td> +<td align="left"><a href="http://www.theserverside.com/tt/articles/article.tss?l=SettingUpMavenRepository"; class="externalLink">Setting up the Internal Repository</a></td> <td>The Server Side</td> @@ -326,7 +326,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="http://www.manuelrecena.com/docs/maven_061106.pdf";>Maven - Menos mal que has venido (in Spanish)</a></td> +<td align="left"><a href="http://www.manuelrecena.com/docs/maven_061106.pdf"; class="externalLink">Maven - Menos mal que has venido (in Spanish)</a></td> <td>Universidad de Sevilla</td> @@ -337,7 +337,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="http://java.developpez.com/faq/maven/";>FAQ for Maven and Continuum (in French)</a></td> +<td align="left"><a href="http://java.developpez.com/faq/maven/"; class="externalLink">FAQ for Maven and Continuum (in French)</a></td> <td>Developpez.com</td> @@ -348,7 +348,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="http://www.javaposse.com/index.php?post_id=112128";>Java Posse #070 - Interview with Brett Porter of Maven</a></td> +<td align="left"><a href="http://www.javaposse.com/index.php?post_id=112128"; class="externalLink">Java Posse #070 - Interview with Brett Porter of Maven</a></td> <td>Java Posse</td> @@ -359,7 +359,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html";>The Maven 2 POM demystified</a></td> +<td align="left"><a href="https://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html"; class="externalLink">The Maven 2 POM demystified</a></td> <td>JavaWorld</td> @@ -370,7 +370,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="https://www.drdobbs.com/architecture-and-design/maven-building-complex-systems/186100398";>Maven: Building Complex Systems</a></td> +<td align="left"><a href="https://www.drdobbs.com/architecture-and-design/maven-building-complex-systems/186100398"; class="externalLink">Maven: Building Complex Systems</a></td> <td>Dr.Dobb's</td> @@ -381,7 +381,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-02-2006/jw-0227-maven.html";>Get the most out of Maven site generation</a></td> +<td align="left"><a href="https://www.javaworld.com/javaworld/jw-02-2006/jw-0227-maven.html"; class="externalLink">Get the most out of Maven site generation</a></td> <td>JavaWorld</td> @@ -392,7 +392,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?lsrc=maven-users";>An introduction to Maven 2</a></td> +<td align="left"><a href="https://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?lsrc=maven-users"; class="externalLink">An introduction to Maven 2</a></td> <td>JavaWorld</td> @@ -403,7 +403,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="https://web.archive.org/web/20051228123436/http://www.onjava.com/pub/a/onjava/2005/09/07/maven.html";>Building J2EE Projects with Maven</a></td> +<td align="left"><a href="https://web.archive.org/web/20051228123436/http://www.onjava.com/pub/a/onjava/2005/09/07/maven.html"; class="externalLink">Building J2EE Projects with Maven</a></td> <td>OnJava</td> @@ -414,7 +414,7 @@ <tr class="a"> -<td align="left"><a class="externalLink" href="https://web.archive.org/web/20041217085616/http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk2.html";>Master and Commander by Julien Dubois</a></td> +<td align="left"><a href="https://web.archive.org/web/20041217085616/http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk2.html"; class="externalLink">Master and Commander by Julien Dubois</a></td> <td>Oracle</td> @@ -425,7 +425,7 @@ <tr class="b"> -<td align="left"><a class="externalLink" href="http://www.internetnews.com/dev-news/article.php/3381841";>Apache's Maven Comes of Age</a> (Coverage of the release of Maven 1.0)</td> +<td align="left"><a href="http://www.internetnews.com/dev-news/article.php/3381841"; class="externalLink">Apache's Maven Comes of Age</a> (Coverage of the release of Maven 1.0)</td> <td>internetnews.com</td>
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 Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/background/history-of-maven.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/background/history-of-maven.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – History of Maven</title> <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="../css/site.css" /> @@ -121,7 +121,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>History of Maven</h1><!-- +<section> +<h1><a name="History_of_Maven"></a>History of Maven</h1><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -146,8 +147,8 @@ under the License. --> <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.qm...@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.qm...@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>Maven began its life in the <a href="http://jakarta.apache.org"; class="externalLink">Jakarta</a> <a href="http://jakarta.apache.org/alexandria/legacy/"; class="externalLink">Alexandria</a> project. The Alexandria project is now defunct but was the breeding ground for not only Maven, but for the <a href="http://gump.apache.org"; class="externalLink">Gump</a> and <a href="http://forrest.apache.org"; class="externalLink">Forrest</a> projects as well. The first import of prototype sources happened in +<a href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200108.mbox/%3c20010827163505.53005.qm...@icarus.apache.org%3e"; class="externalLink">August 2001</a>. As of the date of this document (October 2005) Maven was <a href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200202.mbox/%3c20020202153719.50163.qm...@icarus.apache.org%3e"; class="externalLink">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 href="http://turbine.apache.org/"; class="externalLink">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 @@ -183,7 +184,7 @@ pretty much allowed any project to do wh 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 +<a href="http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html"; class="externalLink">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 disagree 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 @@ -199,12 +200,12 @@ need at runtime between all your differe 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> +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 +After a little hunting I found <a href="http://www.ibiblio.org"; class="externalLink">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 @@ -214,7 +215,7 @@ is very cool.</p> 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> +was written by myself with lots of help from Bob McWhirter</p></section></section> </main> </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 Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/background/philosophy-of-maven.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/background/philosophy-of-maven.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Philosophy of Maven</title> <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="../css/site.css" /> @@ -121,7 +121,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>Philosophy of Maven</h1><!-- +<section> +<h1><a name="Philosophy_of_Maven"></a>Philosophy of Maven</h1><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -168,7 +169,7 @@ to project management. On a very high le and deployed. Of course there is infinite variation in each of the above mentioned steps, but this variation still occurs within the confines of a well defined path and it is this path that Maven attempts to present to everyone in a clear way. The easiest way to make a path clear is to provide people with a set of patterns that -can be shared by anyone involved in a project.</p> +can be shared by anyone involved in a project.</p></section> </main> </div> </div> Modified: maven/website/content/ci-management.html ============================================================================== --- maven/website/content/ci-management.html (original) +++ maven/website/content/ci-management.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.3.0:ci-management at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.3.0:ci-management at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – CI Management</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -127,12 +127,12 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Overview"></a>Overview</h2><a name="Overview"></a> +<h1><a name="Overview"></a>Overview</h1><a name="Overview"></a> <p>This project uses <a class="externalLink" href="https://www.jenkins.io/";>Jenkins</a>.</p></section><section> -<h2><a name="Access"></a>Access</h2><a name="Access"></a> +<h1><a name="Access"></a>Access</h1><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://ci-maven.apache.org/job/Maven/job/maven-box/";>https://ci-maven.apache.org/job/Maven/job/maven-box/</a></pre></div></section><section> -<h2><a name="Notifiers"></a>Notifiers</h2><a name="Notifiers"></a> +<h1><a name="Notifiers"></a>Notifiers</h1><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"> <tr class="a"> Modified: maven/website/content/code-quality-management.html ============================================================================== --- maven/website/content/code-quality-management.html (original) +++ maven/website/content/code-quality-management.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/code-quality-management.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/code-quality-management.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Code Quality Management</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -121,7 +121,7 @@ </div> </header> <main id="bodyColumn" class="span10" > -<section> +<section><section> <h2><a name="Code_Quality_Management"></a>Code Quality Management</h2><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file @@ -142,7 +142,7 @@ under the License. --> <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 +<a href="https://maven.apache.org/plugins/maven-checkstyle-plugin/"; class="externalLink">Checkstyle</a>, <a href="https://maven.apache.org/plugins/maven-pmd-plugin/"; class="externalLink">PMD</a>, <a href="https://mojohaus.org/jdepend-maven-plugin/"; class="externalLink">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> @@ -150,12 +150,12 @@ this information to offer enhanced quali the Maven community:</p> <ul> -<li><a class="externalLink" href="https://hudson-ci.org";>Hudson</a></li> -<li><a class="externalLink" href="https://jenkins-ci.org";>Jenkins</a></li> -<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></section></section> +<li><a href="https://hudson-ci.org"; class="externalLink">Hudson</a></li> +<li><a href="https://jenkins-ci.org"; class="externalLink">Jenkins</a></li> +<li><a href="http://www.sonarqube.org/"; class="externalLink">SonarQube</a></li> +<li><a href="http://www.squale.org/"; class="externalLink">Squale</a></li> +<li><a href="http://xradar.sourceforge.net"; class="externalLink">XRadar</a></li> +</ul></section></section></section> </main> </div> </div> Modified: maven/website/content/community.html ============================================================================== --- maven/website/content/community.html (original) +++ maven/website/content/community.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/community.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/community.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – The Maven Community</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -121,7 +121,7 @@ </div> </header> <main id="bodyColumn" class="span10" > -<section> +<section><section> <h2><a name="The_Maven_Community"></a>The Maven Community</h2><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file @@ -179,7 +179,7 @@ power-users and corporations. The incent 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><em>DO NOT wget THE ENTIRE REPOSITORY!</em></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></section></section><section> @@ -192,8 +192,8 @@ User List is specifically dedicated to a Maven things.</p></section><section> <h4><a name="Slack"></a>Slack</h4> <p>For people actively contributing to Maven, especially committers, there -is <a class="externalLink" href="https://infra.apache.org";>the ASF Slack workspace</a> available to discuss -issues, solve problems and build community in real-time.</p></section></section></section> +is <a href="https://infra.apache.org"; class="externalLink">the ASF Slack workspace</a> available to discuss +issues, solve problems and build community in real-time.</p></section></section></section></section> </main> </div> </div> Modified: maven/website/content/configure.html ============================================================================== --- maven/website/content/configure.html (original) +++ maven/website/content/configure.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/configure.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/configure.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Configuring Apache Maven</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -128,7 +128,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>Configuring Apache Maven</h1><!-- +<section> +<h1><a name="Configuring_Apache_Maven"></a>Configuring Apache Maven</h1><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -206,7 +207,7 @@ configuration options for the <code>mvn< <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></section> +</ul></section></section> </main> </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 Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/committer-environment.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/committer-environment.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Vincent Siveton" /> <meta name="date" content="2006-10-01" /> <title>Maven – Developers centre - Committer Environment</title> @@ -141,22 +141,22 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Introduction"></a>Introduction</h2> +<h1><a name="Introduction"></a>Introduction</h1> <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> +<h1><a name="Source_File_Encoding">Source File Encoding</a></h1> <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> +<h1><a name="Subversion_Configuration"></a>Subversion Configuration</h1> <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> +<h1><a name="Maven_Code_Style">Maven Code Style</a></h1> <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> +<h2><a name="IntelliJ_IDEA_4.5.2B"></a>IntelliJ IDEA 4.5+</h2> <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> +<h2><a name="Eclipse_3.2.2B"></a>Eclipse 3.2+</h2> <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> <p>To ensure a consistent package import order in Java files, download <code><a href="./maven-eclipse.importorder">maven-eclipse.importorder</a></code>, select Window > Preferences and navigate to Java > Code Style > Organize Imports. Click on Import... and select the downloaded file to change the sort order.</p></section></section><section> -<h2><a name="Useful_software"></a>Useful software</h2> +<h1><a name="Useful_software"></a>Useful software</h1> <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> Modified: maven/website/content/developers/committer-settings.html ============================================================================== --- maven/website/content/developers/committer-settings.html (original) +++ maven/website/content/developers/committer-settings.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/committer-settings.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/committer-settings.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Vincent Siveton Dennis Lundberg" /> <meta name="date" content="2011-05-23" /> @@ -142,9 +142,9 @@ Dennis Lundberg" /> </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Introduction"></a>Introduction</h2> +<h1><a name="Introduction"></a>Introduction</h1> <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> +<h2><a name="Enable_Apache_Servers"></a>Enable Apache Servers</h2> <p>Maven uses several servers configuration to deploy snapshots and releases on the Apache servers. You need to tell to Maven what your Apache username is.</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> <div class="source"><pre class="prettyprint linenums"><settings> @@ -165,7 +165,7 @@ Dennis Lundberg" /> ... </servers> </settings></pre></div></section><section> -<h3><a name="Enable_sending_announcement_e-mails"></a>Enable sending announcement e-mails</h3> +<h2><a name="Enable_sending_announcement_e-mails"></a>Enable sending announcement e-mails</h2> <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> ... Modified: maven/website/content/developers/compatibility-plan.html ============================================================================== --- maven/website/content/developers/compatibility-plan.html (original) +++ maven/website/content/developers/compatibility-plan.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/compatibility-plan.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/compatibility-plan.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Hervé Boutemy" /> <meta name="date" content="2020-05-20" /> <title>Maven – Maven Plugins Compatibility Plan</title> @@ -141,20 +141,20 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Maven_Plugins_Compatibility_Plan"></a>Maven Plugins Compatibility Plan</h2><section> -<h3><a name="Scope"></a>Scope</h3> +<h1><a name="Maven_Plugins_Compatibility_Plan"></a>Maven Plugins Compatibility Plan</h1><section> +<h2><a name="Scope"></a>Scope</h2> <p>This page describes the system requirements plan, which consists of:</p> <ol style="list-style-type: decimal"> <li>minimum <b>Java</b> runtime prerequisite for Maven plugins, which can be extended to shared components,</li> <li>minimum <b>Maven</b> runtime prerequisite for plugins.</li></ol> <p>Such requirements are displayed as "System Requirements" in every plugin info report (see <a href="/plugins/maven-clean-plugin/plugin-info.html">this example</a>).</p> <p>Consolidated view for all LATEST plugins release is visible in a <a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-prerequisites.html";>daily generated report</a>.</p></section><section> -<h3><a name="Maven_Plan"></a>Maven Plan</h3> +<h2><a name="Maven_Plan"></a>Maven Plan</h2> <ul> <li>Until 2012, Maven 2.2.1 + Java 5 prerequisites, with plugins versions in 2.x</li> <li>Since 2012, Maven 3.0 + Java 7 prerequisites, with plugins in 3.x.y</li> <li>Since June 2020, Maven Plugin API used by plugins >= 3.1.0 + Java 8 prerequisites <a class="externalLink" href="https://s.apache.org/MVN-PLUGIN-MIGRATION-3.1";>Technical details</a></li></ul></section><section> -<h3><a name="Context"></a>Context</h3> +<h2><a name="Context"></a>Context</h2> <ul> <li>Maven core history with Java prerequisite is available in the <a href="/docs/history.html">release notes</a></li> <li>JDK/JRE availability dates: Modified: maven/website/content/developers/conventions/code.html ============================================================================== --- maven/website/content/developers/conventions/code.html (original) +++ maven/website/content/developers/conventions/code.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/conventions/code.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/conventions/code.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Vincent Siveton" /> <meta name="date" content="2008-07-05" /> <title>Maven – Maven Code Style And Code Conventions</title> @@ -134,9 +134,9 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Maven_Code_Style_And_Code_Conventions"></a>Maven Code Style And Code Conventions</h2> +<h1><a name="Maven_Code_Style_And_Code_Conventions"></a>Maven Code Style And Code Conventions</h1> <p>This document describes how developers and contributors should format code in order to improve consistency, readability and maintainability.</p><section> -<h3><a name="Generic_Code_Style_And_Convention"></a>Generic Code Style And Convention</h3> +<h2><a name="Generic_Code_Style_And_Convention"></a>Generic Code Style And Convention</h2> <p>All working files (java, xml, others) should respect the following conventions:</p> <ul> <li><b>License Header</b>: Always add the current <a class="externalLink" href="https://www.apache.org/legal/src-headers.html#headers";>ASF license header</a> in all files checked into the source code repository.</li> @@ -146,8 +146,8 @@ <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, can 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> +<h2><a name="Java">Java</a></h2><section> +<h3><a name="Java_Code_Style">Java Code Style</a></h3> <p>The Maven style for Java is mainly:</p> <ul> <li><b>White space</b>: One space after control statements and between arguments (e.g. <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> @@ -218,13 +218,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><section> -<h5><a name="IntelliJ_IDEA"></a>IntelliJ IDEA</h5> +<h4><a name="IntelliJ_IDEA"></a>IntelliJ IDEA</h4> <p>Download <code><a href="../../developers/maven-idea-codestyle.xml">maven-idea-codestyle.xml</a></code> and import it into IDEA using File > Settings > Editor > Code Style > Gear icon > Import Scheme > IntelliJ IDEA Code Style XML</p></section><section> -<h5><a name="Eclipse"></a>Eclipse</h5> +<h4><a name="Eclipse"></a>Eclipse</h4> <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> <p>To ensure a package import order consistent with the layout described below, download <code><a href="../../developers/maven-eclipse.importorder">maven-eclipse.importorder</a></code>, select Window > Preferences and navigate to Java > Code Style > Organize Imports. Click on Import... and select the downloaded file to change the import order.</p></section></section><section> -<h4><a name="Java_Code_Convention">Java Code Convention</a></h4> +<h3><a name="Java_Code_Convention">Java Code Convention</a></h3> <p>For consistency reasons, our Java code convention is mainly:</p> <ul> <li><b>Naming</b>: Constants (i.e. static final members) should always be in upper case. Use short, descriptive names for classes and methods.</li> @@ -233,7 +233,7 @@ <li><b>Exceptions</b>: Throw meaningful exceptions to make debugging and testing easier.</li> <li><b>Documentation</b>: Document public interfaces well, i.e. all non-trivial public and protected functions should include Javadoc that indicates what they do.</li> <li><b>Testing</b>: All non-trivial public classes should have corresponding unit or integration tests.</li></ul></section><section> -<h4><a name="Java_Code_Convention_-_import_layouts">Java Code Convention - import layouts</a></h4> +<h3><a name="Java_Code_Convention_-_import_layouts">Java Code Convention - import layouts</a></h3> <p>For consistency reasons, Java imports should be organized as:</p> <ul> <li>import <b>javax.*</b></li> @@ -244,10 +244,10 @@ <li>blank line</li> <li>import <b>static all other imports</b></li></ul> <p>all imports in each group should be sorted alphabetically.</p></section><section> -<h4><a name="JavaDoc_Convention">JavaDoc Convention</a></h4> +<h3><a name="JavaDoc_Convention">JavaDoc Convention</a></h3> <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> +<h2><a name="XML">XML</a></h2><section> +<h3><a name="XML_Code_Style">XML Code Style</a></h3> <p>The Maven style for XML files is mainly:</p> <ul> <li><b>Indentation</b>: Always use 2 space indents, unless you're wrapping a new XML tags line in which case you should indent 4 spaces.</li> @@ -265,9 +265,9 @@ <div class="source"><pre class="prettyprint linenums"> <!-- ====================================================================== --> <!-- Block documentation --> <!-- ====================================================================== --></pre></div></li></ul></section><section> -<h4><a name="Generic_XML_Code_Convention">Generic XML Code Convention</a></h4> +<h3><a name="Generic_XML_Code_Convention">Generic XML Code Convention</a></h3> <p>No generic code convention exists yet for XML files.</p></section><section> -<h4><a name="POM_Code_Convention">POM Code Convention</a></h4> +<h3><a name="POM_Code_Convention">POM Code Convention</a></h3> <p>The team has <a class="externalLink" href="https://lists.apache.org/thread/h8px5t6f3q59cnkzpj1t02wsoynr3ygk";>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> <div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> @@ -321,12 +321,12 @@ <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. <code>org.apache.maven</code>) is a good practice.</li></ol> <p><b>Note</b>: There exist two alternatives 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> +<h3><a name="XDOC_Code_Convention">XDOC Code Convention</a></h3> <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></section><section> -<h4><a name="FML_Code_Convention">FML Code Convention</a></h4> +<h3><a name="FML_Code_Convention">FML Code Convention</a></h3> <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></section></section></section> Modified: maven/website/content/developers/conventions/git.html ============================================================================== --- maven/website/content/developers/conventions/git.html (original) +++ maven/website/content/developers/conventions/git.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/conventions/git.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/conventions/git.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Olivier Lamy" /> <meta name="date" content="2012-09-12" /> <title>Maven – Maven Git Convention</title> @@ -134,10 +134,10 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Maven_Git_Convention"></a>Maven Git Convention</h2> +<h1><a name="Maven_Git_Convention"></a>Maven Git Convention</h1> <p>This document describes how developers should use Git. </p><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> +<h2><a name="Git_Configuration"></a>Git Configuration</h2><section> +<h3><a name="For_contributors_who_are_not_committers"></a>For contributors who are not committers</h3> <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"> @@ -146,9 +146,9 @@ <li>Make a branch named after your JIRA ticket. 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></ol></section><section> -<h4><a name="For_committers"></a>For committers</h4> +<h3><a name="For_committers"></a>For committers</h3> <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> +<h4><a name="Commit_Message_Template">Commit Message Template</a></h4> <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> <div class="source"><pre class="prettyprint linenums">[ISSUE-1] <<Summary field from JIRA>> @@ -160,21 +160,21 @@ o Comments</pre></div> <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></section></section></section></section><section> -<h2><a name="eg:"></a>eg:</h2> +<h1><a name="eg:"></a>eg:</h1> <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><section> -<h3><a name="Apply_User_Patch"></a>Apply User Patch</h3> +<h2><a name="Apply_User_Patch"></a>Apply User Patch</h2> <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></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> +<h2><a name="Edit_Commit_Message"></a>Edit Commit Message</h2></section></section><section> +<h1><a name="to_edit_last_commit_comment:"></a>to edit last commit comment:</h1> <div> <pre>$ git commit --amend -m "new comment"</pre></div><section> -<h3><a name="Workflow"></a>Workflow</h3> +<h2><a name="Workflow"></a>Workflow</h2> <p>Workflow for svn folks is something like :</p> <div> <pre> $ git pull @@ -195,12 +195,12 @@ $ git fetch $ git rebase origin/master // this reapplies your local changes on top of origin/master $ git push</pre></div></section><section> -<h3><a name="Other_useful_Git_commands_while_developing"></a>Other useful Git commands while developing</h3> +<h2><a name="Other_useful_Git_commands_while_developing"></a>Other useful Git commands while developing</h2> <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><section> -<h4><a name="power-git_checkout"></a>power-git checkout</h4> +<h3><a name="power-git_checkout"></a>power-git checkout</h3> <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> <p>Starting with nothing (no existing clone)</p> Modified: maven/website/content/developers/conventions/jira.html ============================================================================== --- maven/website/content/developers/conventions/jira.html (original) +++ maven/website/content/developers/conventions/jira.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/developers/conventions/jira.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/developers/conventions/jira.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Maven JIRA Conventions</title> <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="../../css/site.css" /> @@ -131,7 +131,7 @@ </div> </header> <main id="bodyColumn" class="span10" > -<section> +<section><section> <h2><a name="Maven_JIRA_Conventions"></a>Maven JIRA Conventions</h2><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file @@ -157,15 +157,11 @@ under the License. <ul> <li> - -<p><b>Minor changes</b> such as code reformatting, documentation fixes, etc. that aren't going to impact other users -can be committed without a JIRA issue.</p> -</li> +<p><strong>Minor changes</strong> such as code reformatting, documentation fixes, etc. that aren't going to impact other users +can be committed without a JIRA issue.</p></li> <li> - -<p><b>Larger changes</b> such as bug fixes, API changes, significant refactoring, new classes, and pretty much any change -of more than 100 lines, should have JIRA tickets.</p> -</li> +<p><strong>Larger changes</strong> such as bug fixes, API changes, significant refactoring, new classes, and pretty much any change +of more than 100 lines, should have JIRA tickets.</p></li> </ul> <p>Creating a JIRA issue and referring it in the commit comments simplifies tracking the changes that happen in a release, using JIRA automatic release notes creation.</p></section><section> @@ -173,18 +169,18 @@ using JIRA automatic release notes creat <p>This section presents some conventions about the issue fields.</p><section> <h4><a name="Priority"></a>Priority</h4> <p>Committers have the responsibility to realign priority by editing the issue.</p> -<p><i>Reasoning</i>: having a correct release note</p></section><section> +<p><em>Reasoning</em>: having a correct release note</p></section><section> <h4><a name="Assignee"></a>Assignee</h4> <p>Committers can assign an issue to a specific committer that person seems to be well placed to address it.</p></section><section> <h4><a name="Component.2Fs"></a>Component/s</h4> <p>Committers have the responsibility to specify the correct component by editing the issue.</p> -<p><i>Reasoning</i>: having a correct release note.</p></section><section> +<p><em>Reasoning</em>: 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 also affects preceding versions. For example, an issue that affects Maven 3.6.3 also affects 3.6.0, 3.6.1, 3.6.2. If it is a regression, the committers should specify the affected versions.</p> -<p><i>Reasoning</i>: having a correct release note.</p></section><section> +<p><em>Reasoning</em>: having a correct release note.</p></section><section> <h4><a name="Fix_Version.2Fs"></a>Fix Version/s</h4> <p>Update to correct version after merging to master.</p></section><section> <h4><a name="Time_Tracking"></a>Time Tracking</h4> @@ -192,10 +188,10 @@ If it is a regression, the committers sh <h3><a name="Further_Links"></a>Further Links</h3> <ul> -<li><a class="externalLink" href="https://confluence.atlassian.com/jira064/jira-documentation-720411693.html";>JIRA Documentation</a></li> -<li><a class="externalLink" href="https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html";>What is an Issue?</a></li> -<li><a class="externalLink" href="https://confluence.atlassian.com/jira064/what-is-a-project-720416135.html";>What is a project?</a></li> -</ul></section></section> +<li><a href="https://confluence.atlassian.com/jira064/jira-documentation-720411693.html"; class="externalLink">JIRA Documentation</a></li> +<li><a href="https://confluence.atlassian.com/jira064/what-is-an-issue-720416138.html"; class="externalLink">What is an Issue?</a></li> +<li><a href="https://confluence.atlassian.com/jira064/what-is-a-project-720416135.html"; class="externalLink">What is a project?</a></li> +</ul></section></section></section> </main> </div> </div> Modified: maven/website/content/developers/dependency-policies.html ============================================================================== --- maven/website/content/developers/dependency-policies.html (original) +++ maven/website/content/developers/dependency-policies.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/dependency-policies.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/dependency-policies.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Stephen Connolly" /> <meta name="date" content="2011-02-01" /> <title>Maven – Maven Dependency Policies</title> @@ -141,24 +141,24 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Maven_Dependency_Policies"></a>Maven Dependency Policies</h2><section> -<h3><a name="Scope"></a>Scope</h3> +<h1><a name="Maven_Dependency_Policies"></a>Maven Dependency Policies</h1><section> +<h2><a name="Scope"></a>Scope</h2> <p>This page describes the policies around the use of dependencies by the Apache Maven Developers in the process of developing Apache Maven itself.</p> <p>This page does not apply to projects hosted outside of the Apache Maven project. In order to remove all doubt, this page only applies to code which has a Github URL that starts with <code>https://github.com/apache/maven</code> or a Gitbox URL starting with <code>https://gitbox.apache.org/repos/asf?p=maven</code></p> <p>If you have stumbled across this page and you are working on code that does not have a Github URL starting with <code>https://github.com/apache/maven</code> then this page does not apply to you.</p></section><section> -<h3><a name="Background"></a>Background</h3> +<h2><a name="Background"></a>Background</h2> <p>The Apache Maven PMC is tasked with ensuring (among other things) that all legal issues are addressed and that each and every release is the product of the community as a whole.</p> <p>The Apache Maven project consists of quite a number of components. For the purposes of this policy, we will make a distinction between the core Maven distribution and all the other components.</p> <p>The core Maven distribution is the binary and source distributions made available from the https://maven.apache.org/download page. </p></section><section> -<h3><a name="Applicability"></a>Applicability</h3> +<h2><a name="Applicability"></a>Applicability</h2> <p>This policy applies to all changes to dependencies as and from Subversion revision 1067464.</p></section><section> -<h3><a name="Core_Maven_Distribution_Dependencies"></a>Core Maven Distribution Dependencies</h3> +<h2><a name="Core_Maven_Distribution_Dependencies"></a>Core Maven Distribution Dependencies</h2> <p>All dependencies which are included in the Core Maven Distribution must either:</p> <ul> <li>be licensed under a <a class="externalLink" href="https://www.apache.org/legal/resolved.html#category-a";>Category A license</a>; or</li> <li>be licensed under a <a class="externalLink" href="https://www.apache.org/legal/resolved.html#category-b";>Category B license</a> and approved by a majority vote of the Apache Maven PMC.</li></ul> <p>Votes for Category B licenses will be held on the d...@maven.apache.org mailing list. A majority of the PMC must vote in favour of a Category B licensed dependency before a release can be made containing that dependency.</p></section><section> -<h3><a name="Non-Core_Dependencies"></a>Non-Core Dependencies</h3> +<h2><a name="Non-Core_Dependencies"></a>Non-Core Dependencies</h2> <p>Non-Core components may only use Category A or Category B licenses.</p></section></section> </main> </div> Modified: maven/website/content/developers/index.html ============================================================================== --- maven/website/content/developers/index.html (original) +++ maven/website/content/developers/index.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/index.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/index.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Vincent Siveton Brett Porter" /> <meta name="date" content="2015-02-14" /> @@ -135,10 +135,10 @@ Brett Porter" /> </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Maven_Developer_Centre"></a>Maven Developer Centre</h2> +<h1><a name="Maven_Developer_Centre"></a>Maven Developer Centre</h1> <p>This documentation centre is for people who are Maven developers, or would like to contribute.</p> <p>If you cannot find your answers here, feel free to ask the <a class="externalLink" href="mailto:d...@maven.apache.org";>Maven Developer List</a>.</p><section> -<h3><a name="Contributors_Resources"></a>Contributors Resources</h3> +<h2><a name="Contributors_Resources"></a>Contributors Resources</h2> <ul> <li><a href="../guides/development/guide-helping.html">Guide to helping with Maven</a></li> <li><a href="../guides/development/guide-maven-development.html">Developing Maven</a></li> @@ -147,8 +147,8 @@ Brett Porter" /> <li><a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/";>Continuous Integration</a></li> <li><a href="../plugin-developers/common-bugs.html">Common Bugs and Pitfalls</a></li> <li><a href="../project-roles.html">Apache Maven Project Roles</a></li></ul></section><section> -<h3><a name="Committers_Resources"></a>Committers Resources</h3><section> -<h4><a name="General_Resources"></a>General Resources</h4> +<h2><a name="Committers_Resources"></a>Committers Resources</h2><section> +<h3><a name="General_Resources"></a>General Resources</h3> <ul> <li><a href="./welcome-to-new-committers.html">Guide for new Maven committers</a></li> <li><a href="./committer-environment.html">Committer Environment</a></li> @@ -157,21 +157,21 @@ Brett Porter" /> <li><a href="./dependency-policies.html">Maven Dependency Policies</a></li> <li><a href="./compatibility-plan.html">Maven Plugins and Components Compatibility Plan</a></li> <li><a class="externalLink" href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=5964567";>Maven Proposals/Backlog</a></li></ul></section></section><section> -<h3><a name="Developers_Conventions"></a>Developers Conventions</h3> +<h2><a name="Developers_Conventions"></a>Developers Conventions</h2> <p>There are a number of conventions used in the Maven projects, which contributors and developers alike should follow for consistency's sake.</p> <ul> <li><a href="./conventions/code.html">Maven Code Style And Conventions</a></li> <li><a href="./conventions/jira.html">Maven JIRA Convention</a></li> <li><a href="./conventions/git.html">Maven Git Convention</a></li></ul> <p><b>Note</b>: If you cannot find your answers here, feel free to ask the <a class="externalLink" href="mailto:d...@maven.apache.org";>Maven Developer List</a>.</p></section><section> -<h3><a name="Making_Releases"></a>Making Releases</h3> +<h2><a name="Making_Releases"></a>Making Releases</h2> <ul> <li><a href="./release/pmc-gpg-keys.html">Making GPG Keys</a></li> <li><a href="./release/index.html">Release Process</a></li></ul></section><section> -<h3><a name="Maven_Website"></a>Maven Website</h3> +<h2><a name="Maven_Website"></a>Maven Website</h2> <ul> <li><a href="./website/index.html">Deploy Maven Website</a></li></ul></section><section> -<h3><a name="Other_Resources"></a>Other Resources</h3> +<h2><a name="Other_Resources"></a>Other Resources</h2> <ul> <li><a class="externalLink" href="https://www.apache.org/dev/";>ASF Development Infrastructure Information</a></li> <li><a class="externalLink" href="https://www.apache.org/foundation/";>About the Apache Software Foundation</a></li></ul></section></section> Modified: maven/website/content/developers/mojo-api-specification.html ============================================================================== --- maven/website/content/developers/mojo-api-specification.html (original) +++ maven/website/content/developers/mojo-api-specification.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/xdoc/developers/mojo-api-specification.xml at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/xdoc/developers/mojo-api-specification.xml at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="John Casey" /> <title>Maven – Mojo API Specification</title> <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.0.min.css" /> @@ -137,7 +137,7 @@ <section> -<h2><a name="Introduction"></a>Introduction</h2> +<h1><a name="Introduction"></a>Introduction</h1> <p>Maven plugins can be written in Java or any of a number of scripting languages. Plugins consists of one or more Mojos, @@ -185,9 +185,9 @@ </section> <section> -<h2><a name="API_Documentation"></a>API Documentation</h2> +<h1><a name="API_Documentation"></a>API Documentation</h1> <section> -<h3><a name="org.apache.maven.plugin.Mojo"></a>org.apache.maven.plugin.Mojo</h3> +<h2><a name="org.apache.maven.plugin.Mojo"></a>org.apache.maven.plugin.Mojo</h2> <p>This interface forms the contract required for Mojos to interact with the Maven infrastructure. It features an @@ -204,8 +204,7 @@ logging mechanism which will allow the Mojo to communicate to the outside world through standard Maven channels. </p> - <section><section><section> -<h6><a name="Method_Summary:"></a>Method Summary:</h6> + Method Summary: <ul> @@ -243,9 +242,9 @@ </p> </li> </ul> - </section></section></section></section> + </section> <section> -<h3><a name="org.apache.maven.plugin.AbstractMojo"></a>org.apache.maven.plugin.AbstractMojo</h3> +<h2><a name="org.apache.maven.plugin.AbstractMojo"></a>org.apache.maven.plugin.AbstractMojo</h2> <p>Currently, this abstract base class simply takes care of managing the Maven log for concrete derivations. In keeping with this, it @@ -256,8 +255,7 @@ , to furnish Log access to these concrete implementations. </p> - <section><section><section> -<h6><a name="Method_Summary:"></a>Method Summary:</h6> + Method Summary: <ul> @@ -302,9 +300,9 @@ </p> </li> </ul> - </section></section></section></section> + </section> <section> -<h3><a name="org.apache.maven.plugin.logging.Log"></a>org.apache.maven.plugin.logging.Log</h3> +<h2><a name="org.apache.maven.plugin.logging.Log"></a>org.apache.maven.plugin.logging.Log</h2> <p>This interface supplies the API for providing feedback to the user from the Mojo, using standard Maven channels. There should be no big @@ -320,8 +318,7 @@ <code>toString()</code> . </p> - <section><section><section> -<h6><a name="Method_Summary:"></a>Method Summary:</h6> + Method Summary: <ul> @@ -453,10 +450,10 @@ </p> </li> </ul> - </section></section></section></section> + </section> </section> <section> -<h2><a name="The_Descriptor_and_Annotations"></a>The Descriptor and Annotations</h2> +<h1><a name="The_Descriptor_and_Annotations"></a>The Descriptor and Annotations</h1> <p>In addition to the normal Java requirements in terms of interfaces and/or abstract base classes which need to be implemented, a plugin @@ -667,7 +664,7 @@ <td> Defines a default phase to bind a mojo execution to if the user does not explicitly set a phase in the POM. - <i>Note:</i> This annotation will not automagically make a mojo run when the plugin declaration is added + <em>Note:</em> This annotation will not automagically make a mojo run when the plugin declaration is added to the POM. It merely enables the user to omit the <code><phase></code> element from the surrounding <code><execution></code> element. </td> @@ -1136,7 +1133,7 @@ </p> </section> <section> -<h2><a name="Plugin_Tools"></a>Plugin Tools</h2> +<h1><a name="Plugin_Tools"></a>Plugin Tools</h1> <p>By now, we've mentioned the plugin tools several times without telling you what they are or how to use them. Instead of manually writing (and @@ -1152,7 +1149,7 @@ create plugin artifacts.</p> </section> <section> -<h2><a name="Project_Descriptor_.28POM.29_Requirements"></a>Project Descriptor (POM) Requirements</h2> +<h1><a name="Project_Descriptor_.28POM.29_Requirements"></a>Project Descriptor (POM) Requirements</h1> <p>From the POM, Maven plugin projects look quite similar to any other project. For pure Java plugins, the differences are even smaller than @@ -1223,7 +1220,7 @@ </p> </section> <section> -<h2><a name="IDE_integration"></a>IDE integration</h2> +<h1><a name="IDE_integration"></a>IDE integration</h1> <p>If you're using JetBrains IntelliJ IDEA to develop your plugin, you can use the following to configure the javadoc annotations as live @@ -1249,7 +1246,7 @@ </ol> </section> <section> -<h2><a name="Resources"></a>Resources</h2> +<h1><a name="Resources"></a>Resources</h1> <p>This section simply gives a listing of pointers for more information.</p> @@ -1257,22 +1254,22 @@ <ul> <li>QDox Project (Javadoc annotations) [ - <a class="externalLink" href="https://github.com/paul-hammant/qdox";>link</a> + <a href="https://github.com/paul-hammant/qdox"; class="externalLink">link</a> ] </li> <li>Plexus Project (Plexus container) [ - <a class="externalLink" href="https://codehaus-plexus.github.io/";>link</a> + <a href="https://codehaus-plexus.github.io/"; class="externalLink">link</a> ] </li> <li>Maven Plugin API [ - <a class="externalLink" href="https://maven.apache.org/ref/current/maven-plugin-api/apidocs/index.html";>link</a> + <a href="https://maven.apache.org/ref/current/maven-plugin-api/apidocs/index.html"; class="externalLink">link</a> ] </li> <li>MojoDescriptor API [ - <a class="externalLink" href="https://maven.apache.org/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/MojoDescriptor.html";>link</a> + <a href="https://maven.apache.org/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/MojoDescriptor.html"; class="externalLink">link</a> ] </li> </ul> Modified: maven/website/content/developers/release/index.html ============================================================================== --- maven/website/content/developers/release/index.html (original) +++ maven/website/content/developers/release/index.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/developers/release/index.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/release/index.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Jason van Zyl" /> <meta name="date" content="2010-07-26" /> <title>Maven – Releasing A Maven Project</title> @@ -140,7 +140,7 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Releasing_A_Maven_Project"></a>Releasing A Maven Project</h2> +<h1><a name="Releasing_A_Maven_Project"></a>Releasing A Maven Project</h1> <p>What follows is a description of releasing a Maven project to a staging repository and its documentation, whereupon it is scrutinized by the community, approved, and transferred to a production repository.</p> <p>The steps involved are similar for any Apache project, with more specifics for parent POMs and Maven itself. The steps involved, and the relevant documents for each, are listed below.</p> <ul>
