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 2023/02/08 20:32:15 UTC
svn commit: r1907529 [3/22] - in /maven/website/content: ./ apache-resource-bundles/ archives/maven-2.x/ background/ developers/ developers/conventions/ developers/release/ developers/website/ docs/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2/ doc...
Modified: maven/website/content/background/history-of-maven.html
==============================================================================
--- maven/website/content/background/history-of-maven.html (original)
+++ maven/website/content/background/history-of-maven.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/background/history-of-maven.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/background/history-of-maven.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – History of Maven</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="History_of_Maven"></a>History of Maven</h1><!--
+<h1>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,7 +146,7 @@ under the License.
12 October 2005
-->
<section>
-<h2><a name="History_of_Maven_by_Jason_van_Zyl"></a>History of Maven by Jason van Zyl</h2>
+<h2>History of Maven by Jason van Zyl</h2>
<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.qmail@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.qmail@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
@@ -200,7 +200,7 @@ 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
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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/background/philosophy-of-maven.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/background/philosophy-of-maven.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Philosophy of Maven</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Philosophy_of_Maven"></a>Philosophy of Maven</h1><!--
+<h1>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
Modified: maven/website/content/ci-management.html
==============================================================================
--- maven/website/content/ci-management.html (original)
+++ maven/website/content/ci-management.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.1:ci-management at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.1:ci-management at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – CI Management</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -127,20 +127,20 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Overview"></a>Overview</h1><a name="Overview"></a>
+<h1>Overview</h1><a id="Overview"></a>
<p>This project uses <a class="externalLink" href="https://www.jenkins.io/">Jenkins</a>.</p></section><section>
-<h1><a name="Access"></a>Access</h1><a name="Access"></a>
+<h1>Access</h1><a id="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>
-<h1><a name="Notifiers"></a>Notifiers</h1><a name="Notifiers"></a>
+<h1>Notifiers</h1><a id="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">
+<table class="table table-striped">
<tr class="a">
<th>Type</th>
<th>Address</th>
<th>Configuration</th></tr>
<tr class="b">
-<td align="left">mail</td>
+<td style="text-align: left;">mail</td>
<td>-</td>
<td>address=notifications@maven.apache.org</td></tr></table></section>
</main>
Modified: maven/website/content/code-quality-management.html
==============================================================================
--- maven/website/content/code-quality-management.html (original)
+++ maven/website/content/code-quality-management.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/code-quality-management.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/code-quality-management.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Code Quality Management</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section><section>
-<h2><a name="Code_Quality_Management"></a>Code Quality Management</h2><!--
+<h2>Code Quality Management</h2><!--
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
@@ -142,10 +142,10 @@ under the License.
-->
<p>Some existing Maven plugins use code analysis technologies (like
-<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
+<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>
+<h3>Quality management technologies and platforms</h3>
<p>Following is an alphabetical list of those we've heard mentioned around
the Maven community:</p>
<ul>
Modified: maven/website/content/community.html
==============================================================================
--- maven/website/content/community.html (original)
+++ maven/website/content/community.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/community.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/community.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – The Maven Community</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section><section>
-<h2><a name="The_Maven_Community"></a>The Maven Community</h2><!--
+<h2>The Maven Community</h2><!--
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
@@ -147,29 +147,29 @@ report defects, communicate use cases, w
and assist other users in need. This is a quick guide outlining
what members of the Maven community can do to make the system work
better for everyone.</p><section>
-<h3><a name="Helping_With_Maven"></a>Helping With Maven</h3>
+<h3>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><section>
-<h4><a name="Commit_Questions_or_Answers_to_the_Maven_User_FAQ"></a>Commit Questions or Answers to the Maven User FAQ</h4>
+<h4>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></section><section>
-<h4><a name="Help_Log_Defects_in_JIRA"></a>Help Log Defects in JIRA</h4>
+<h4>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></section><section>
-<h4><a name="Developers"></a>Developers</h4>
+<h4>Developers</h4>
<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>
+<h3>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><section>
-<h4><a name="Be_a_Kind_Public_Repository_User"></a>Be a Kind Public Repository User</h4>
+<h4>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
@@ -183,14 +183,14 @@ said, keep the following sentiment in mi
<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>
+<h3>User Gathering Spots</h3>
<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>
+<h4>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></section><section>
-<h4><a name="Slack"></a>Slack</h4>
+<h4>Slack</h4>
<p>For people actively contributing to Maven, especially committers, there
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>
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/configure.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/configure.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Configuring Apache Maven</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -129,7 +129,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Configuring_Apache_Maven"></a>Configuring Apache Maven</h1><!--
+<h1>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
@@ -150,22 +150,22 @@ under the License.
<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><code>MAVEN_OPTS</code> environment variable:</h2>
+<h2><code>MAVEN_OPTS</code> 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 it. E.g. JVM memory
settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
-<h2><a name="MAVEN_ARGS_environment_variable:"></a><code>MAVEN_ARGS</code> environment variable:</h2>
+<h2><code>MAVEN_ARGS</code> environment variable:</h2>
<p>Starting with Maven 4, this variable contains arguments passed to Maven before
CLI arguments. E.g., options and goals could be defined with the value
<code>-B -V checkstyle:checkstyle</code>.</p></section><section>
-<h2><a name="settings.xml_file:"></a><code>settings.xml</code> file:</h2>
+<h2><code>settings.xml</code> 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_directory:"></a><code>.mvn</code> directory:</h2>
+<h2><code>.mvn</code> directory:</h2>
<p>Located within the project's top level directory, the files <code>maven.config</code>, <code>jvm.config</code>, and <code>extensions.xml</code>
contain project specific configuration for running Maven.</p>
<p>This directory 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><code>.mvn/extensions.xml</code> file:</h3>
+<h3><code>.mvn/extensions.xml</code> 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 <code>${MAVEN_HOME}/lib/ext</code> directory. 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
@@ -183,20 +183,20 @@ options to your Maven build every time y
</extensions>
</code></pre></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></section><section>
-<h3><a name="a.mvn.2Fmaven.config_file:"></a><code>.mvn/maven.config</code> file:</h3>
+<h3><code>.mvn/maven.config</code> 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 <code>${maven.projectBasedir}/.mvn/maven.config</code> file which contains the
configuration options for the <code>mvn</code> command line.</p>
<p>For example things like <code>-T3 -U --fail-at-end</code>. So you only have to call Maven just by using <code>mvn clean package</code> instead of <code>mvn -T3 -U --fail-at-end clean package</code> and not to miss the <code>-T3 -U --fail-at-end</code> options on every call. The
<code>${maven.projectBasedir}/.mvn/maven.config</code> is located in the <code>${maven.projectBasedir}/.mvn/</code> directory; also works if in the root of a multi module build.</p></section><section>
-<h3><a name="a.mvn.2Fjvm.config_file:"></a><code>.mvn/jvm.config</code> file:</h3>
+<h3><code>.mvn/jvm.config</code> file:</h3>
<p>Starting with Maven 3.3.1+ you can define JVM configuration via <code>${maven.projectBasedir}/.mvn/jvm.config</code> 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 <code>MAVEN_OPTS</code>, <code>.mavenrc</code> files. So for example if you put the following JVM options into the <code>${maven.projectBasedir}/.mvn/jvm.config</code> file</p>
<div class="source"><pre class="prettyprint linenums"><code>-Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
</code></pre></div>
<p>You don't need to use these options in <code>MAVEN_OPTS</code> or switch between different configurations.</p></section></section><section>
-<h2><a name="Other_guides"></a>Other guides</h2>
+<h2>Other guides</h2>
<p>The following guides contain further information to specific configuration aspects:</p>
<ul>
Modified: maven/website/content/developers/committer-environment.html
==============================================================================
--- maven/website/content/developers/committer-environment.html (original)
+++ maven/website/content/developers/committer-environment.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/committer-environment.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/committer-environment.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Vincent Siveton" />
<meta name="date" content="2006-10-01" />
<title>Maven – Developers centre - Committer Environment</title>
@@ -141,14 +141,14 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Committer_Environment"></a>Committer Environment</h1><section>
-<h2><a name="Introduction"></a>Introduction</h2>
+<h1>Committer Environment</h1><section>
+<h2>Introduction</h2>
<p>This document describes how to set up the Maven committer environment.</p></section><section>
-<h2><a name="Source_File_Encoding"></a>Source File Encoding</h2>
+<h2>Source File Encoding</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 that can encode all characters that Java can handle. The source files should not contain the byte order mark (BOM). There are exceptions to this general rule. For instance, properties files are encoded using ISO-8859-1 as per the JRE API, so please keep this in mind, too.</p></section><section>
-<h2><a name="Maven_Code_Style"></a>Maven Code Style</h2>
+<h2>Maven Code Style</h2>
<p>Refer to <a href="./conventions/code.html">Maven Code Style And Code Conventions</a></p></section><section>
-<h2><a name="Useful_software"></a>Useful software</h2>
+<h2>Useful software</h2>
<p>The Maven Team uses assorted software. Here is a partial list:</p>
<ul>
<li><a class="externalLink" href="https://www.cygwin.com/">Cygwin</a>: collection of free software tools that 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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/committer-settings.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/committer-settings.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<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>
-<h1><a name="Introduction"></a>Introduction</h1>
+<h1>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>
-<h2><a name="Enable_Apache_Servers"></a>Enable Apache Servers</h2>
+<h2>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>
-<h2><a name="Enable_sending_announcement_e-mails"></a>Enable sending announcement e-mails</h2>
+<h2>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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/compatibility-plan.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/compatibility-plan.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<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>
-<h1><a name="Maven_Plugins_Compatibility_Plan"></a>Maven Plugins Compatibility Plan</h1><section>
-<h2><a name="Scope"></a>Scope</h2>
+<h1>Maven Plugins Compatibility Plan</h1><section>
+<h2>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>
-<h2><a name="Maven_Plan"></a>Maven Plan</h2>
+<h2>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>
-<h2><a name="Context"></a>Context</h2>
+<h2>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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/conventions/code.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/conventions/code.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Vincent Siveton" />
<meta name="date" content="2008-07-05" />
<title>Maven – Maven Code Style And Code Conventions</title>
@@ -134,7 +134,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Code_Style_And_Code_Conventions"></a>Maven Code Style And Code Conventions</h1>
+<h1>Maven Code Style And Code Conventions</h1>
<p>This document describes the rules for how the sources should be formatted in order to improve consistency, readability and maintainability.</p>
<p>As the formatting is automatically enforced or even applied with <a class="externalLink" href="https://github.com/diffplug/spotless/tree/main/plugin-maven">spotless-maven-plugin</a> for all projects using <a href="/pom/maven/index.html">Maven Project Parent POM 38 or newer</a> developers usually don't need to care and the following sections are just for informational purposes.</p>
<p>Optionally you can still import the code style formatter for your IDE from <a class="externalLink" href="https://gitbox.apache.org/repos/asf?p=maven-shared-resources.git;a=tree;f=src/main/resources/config;hb=HEAD">shared-resources</a></p>
@@ -153,7 +153,7 @@
<li><a href="#POM_Code_Convention">POM Code Convention</a></li>
<li><a href="#XDOC_Code_Convention">XDOC Code Convention</a></li>
<li><a href="#FML_Code_Convention">FML Code Convention</a></li></ul></li></ul><section>
-<h2><a name="Generic_Code_Style_And_Convention"></a>Generic Code Style And Convention</h2>
+<h2>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>
@@ -163,10 +163,10 @@
<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>
-<h2><a name="Java">Java</a></h2><section>
-<h3><a name="Java_Code_Style">Java Code Style</a></h3>
+<h2><a id="Java">Java</a></h2><section>
+<h3><a id="Java_Code_Style">Java Code Style</a></h3>
<p>Maven adopts the <a class="externalLink" href="https://github.com/palantir/palantir-java-format">palantir Java format</a>.</p></section><section>
-<h3><a name="Java_Code_Convention">Java Code Convention</a></h3>
+<h3><a id="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>
@@ -175,7 +175,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>
-<h3><a name="Java_Code_Convention_-_import_layouts">Java Code Convention - import layouts</a></h3>
+<h3><a id="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>
@@ -184,10 +184,10 @@
<li>import <b>all other imports</b></li></ul>
<p>all imports in each group should be sorted alphabetically.</p>
<p>To ensure a package import order consistent with the layout described above, download <code><a class="externalLink" href="https://gitbox.apache.org/repos/asf?p=maven-shared-resources.git;a=blob_plain;f=src/main/resources/config/maven-eclipse-importorder.txt;hb=HEAD">maven-eclipse-importorder.txt</a></code>, select <i>Window > Preferences</i> and navigate to <i>Java > Code Style > Organize Imports</i>. Click on <i>Import...</i> and select the downloaded file to change the import order.</p></section><section>
-<h3><a name="JavaDoc_Convention">JavaDoc Convention</a></h3>
+<h3><a id="JavaDoc_Convention">JavaDoc Convention</a></h3>
<p>TO BE DISCUSSED</p></section></section><section>
-<h2><a name="XML">XML</a></h2><section>
-<h3><a name="XML_Code_Style">XML Code Style</a></h3>
+<h2><a id="XML">XML</a></h2><section>
+<h3><a id="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>
@@ -205,9 +205,9 @@
<div class="source"><pre class="prettyprint linenums"> <!-- ====================================================================== -->
<!-- Block documentation -->
<!-- ====================================================================== --></pre></div></li></ul></section><section>
-<h3><a name="Generic_XML_Code_Convention">Generic XML Code Convention</a></h3>
+<h3><a id="Generic_XML_Code_Convention">Generic XML Code Convention</a></h3>
<p>No generic code convention exists yet for XML files.</p></section><section>
-<h3><a name="POM_Code_Convention">POM Code Convention</a></h3>
+<h3><a id="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">
@@ -260,12 +260,12 @@
<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. <code>org.apache.maven</code>) is a good practice.</li></ol></section><section>
-<h3><a name="XDOC_Code_Convention">XDOC Code Convention</a></h3>
+<h3><a id="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>
-<h3><a name="FML_Code_Convention">FML Code Convention</a></h3>
+<h3><a id="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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/conventions/git.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/conventions/git.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<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>
-<h1><a name="Maven_Git_Convention"></a>Maven Git Convention</h1>
+<h1>Maven Git Convention</h1>
<p>This document describes how developers should use Git. </p><section>
-<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>
+<h2>Git Configuration</h2><section>
+<h3>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>
-<h3><a name="For_committers"></a>For committers</h3>
+<h3>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>
-<h4><a name="Commit_Message_Template">Commit Message Template</a></h4>
+<h4><a id="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>
@@ -167,17 +167,17 @@ o Comments</pre></div>
Submitted by: Baz Bazman
o Applied without change</pre></div></section></section></section><section>
-<h2><a name="Apply_User_Patch"></a>Apply User Patch</h2>
+<h2>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>
<pre> Closes #NNN.</pre></div>
<p>where NNN is the number of the pull request.</p></section><section>
-<h2><a name="Edit_Commit_Message"></a>Edit Commit Message</h2>
+<h2>Edit Commit Message</h2>
<p>to edit last commit comment:</p>
<div>
<pre>$ git commit --amend -m "new comment"</pre></div></section><section>
-<h2><a name="Workflow"></a>Workflow</h2>
+<h2>Workflow</h2>
<p>Workflow for svn folks is something like :</p>
<div>
<pre> $ git pull
@@ -198,12 +198,12 @@ $ git fetch
$ git rebase origin/master
// this reapplies your local changes on top of origin/master
$ git push</pre></div></section><section>
-<h2><a name="Other_useful_Git_commands_while_developing"></a>Other useful Git commands while developing</h2>
+<h2>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>
-<h3><a name="power-git_checkout"></a>power-git checkout</h3>
+<h3>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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/developers/conventions/jira.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/conventions/jira.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven JIRA Conventions</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../../css/site.css" />
@@ -132,7 +132,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section><section>
-<h2><a name="Maven_JIRA_Conventions"></a>Maven JIRA Conventions</h2><!--
+<h2>Maven JIRA Conventions</h2><!--
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
@@ -152,7 +152,7 @@ under the License.
-->
<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>
+<h3>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>
@@ -165,27 +165,27 @@ of more than 100 lines, should have JIRA
</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>
-<h3><a name="How_To_Use_Issue_Details.3F"></a>How To Use Issue Details?</h3>
+<h3>How To Use Issue Details?</h3>
<p>This section presents some conventions about the issue fields.</p><section>
-<h4><a name="Priority"></a>Priority</h4>
+<h4>Priority</h4>
<p>Committers have the responsibility to realign priority by editing the issue.</p>
<p><em>Reasoning</em>: having a correct release note</p></section><section>
-<h4><a name="Assignee"></a>Assignee</h4>
+<h4>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>
+<h4>Component/s</h4>
<p>Committers have the responsibility to specify the correct component by editing the issue.</p>
<p><em>Reasoning</em>: having a correct release note.</p></section><section>
-<h4><a name="Affects_Version.2Fs"></a>Affects Version/s</h4>
+<h4>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><em>Reasoning</em>: having a correct release note.</p></section><section>
-<h4><a name="Fix_Version.2Fs"></a>Fix Version/s</h4>
+<h4>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>
+<h4>Time Tracking</h4>
<p>The Maven team doesn't use this. Committers can if it helps them.</p></section></section><section>
-<h3><a name="Further_Links"></a>Further Links</h3>
+<h3>Further Links</h3>
<ul>
<li><a href="https://confluence.atlassian.com/jira064/jira-documentation-720411693.html" class="externalLink">JIRA Documentation</a></li>
Modified: maven/website/content/developers/dependency-policies.html
==============================================================================
--- maven/website/content/developers/dependency-policies.html (original)
+++ maven/website/content/developers/dependency-policies.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/dependency-policies.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/dependency-policies.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<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>
-<h1><a name="Maven_Dependency_Policies"></a>Maven Dependency Policies</h1><section>
-<h2><a name="Scope"></a>Scope</h2>
+<h1>Maven Dependency Policies</h1><section>
+<h2>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>
-<h2><a name="Background"></a>Background</h2>
+<h2>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>
-<h2><a name="Applicability"></a>Applicability</h2>
+<h2>Applicability</h2>
<p>This policy applies to all changes to dependencies as and from Subversion revision 1067464.</p></section><section>
-<h2><a name="Core_Maven_Distribution_Dependencies"></a>Core Maven Distribution Dependencies</h2>
+<h2>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 dev@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>
-<h2><a name="Non-Core_Dependencies"></a>Non-Core Dependencies</h2>
+<h2>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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/index.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/index.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<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>
-<h1><a name="Maven_Developer_Centre"></a>Maven Developer Centre</h1>
+<h1>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:dev@maven.apache.org">Maven Developer List</a>.</p><section>
-<h2><a name="Contributors_Resources"></a>Contributors Resources</h2>
+<h2>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>
-<h2><a name="Committers_Resources"></a>Committers Resources</h2><section>
-<h3><a name="General_Resources"></a>General Resources</h3>
+<h2>Committers Resources</h2><section>
+<h3>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>
-<h2><a name="Developers_Conventions"></a>Developers Conventions</h2>
+<h2>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:dev@maven.apache.org">Maven Developer List</a>.</p></section><section>
-<h2><a name="Making_Releases"></a>Making Releases</h2>
+<h2>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>
-<h2><a name="Maven_Website"></a>Maven Website</h2>
+<h2>Maven Website</h2>
<ul>
<li><a href="./website/index.html">Deploy Maven Website</a></li></ul></section><section>
-<h2><a name="Other_Resources"></a>Other Resources</h2>
+<h2>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 Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/xdoc/developers/mojo-api-specification.xml at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/xdoc/developers/mojo-api-specification.xml at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="John Casey" />
<title>Maven – Mojo API Specification</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
@@ -138,7 +138,7 @@
<section>
-<h1><a name="Introduction"></a>Introduction</h1>
+<h1>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,
@@ -186,9 +186,9 @@
</section>
<section>
-<h1><a name="API_Documentation"></a>API Documentation</h1>
+<h1>API Documentation</h1>
<section>
-<h2><a name="org.apache.maven.plugin.Mojo"></a>org.apache.maven.plugin.Mojo</h2>
+<h2>org.apache.maven.plugin.Mojo</h2>
<p>This interface forms the contract required for Mojos to interact
with the Maven infrastructure. It features an
@@ -245,7 +245,7 @@
</ul>
</section>
<section>
-<h2><a name="org.apache.maven.plugin.AbstractMojo"></a>org.apache.maven.plugin.AbstractMojo</h2>
+<h2>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
@@ -303,7 +303,7 @@
</ul>
</section>
<section>
-<h2><a name="org.apache.maven.plugin.logging.Log"></a>org.apache.maven.plugin.logging.Log</h2>
+<h2>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
@@ -454,7 +454,7 @@
</section>
</section>
<section>
-<h1><a name="The_Descriptor_and_Annotations"></a>The Descriptor and Annotations</h1>
+<h1>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
@@ -488,7 +488,7 @@
<code>META-INF/maven/plugin.xml</code>, and it must contain the following:
</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<tr class="a">
@@ -501,7 +501,7 @@
<tr class="b">
-<td align="left"><code>mojos</code></td>
+<td><code>mojos</code></td>
<td>Yes</td>
@@ -520,7 +520,7 @@
<tr class="a">
-<td align="left"><code>dependencies</code></td>
+<td><code>dependencies</code></td>
<td>Yes</td>
@@ -541,7 +541,7 @@
<p>Each Mojo specified inside a plugin descriptor must provide the
following (annotations specified here are at the class level):</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<tr class="a">
@@ -557,7 +557,7 @@
<tr class="b">
-<td align="left"><code>aggregator</code></td>
+<td><code>aggregator</code></td>
<td><code>@aggregator</code></td>
@@ -569,7 +569,7 @@
<tr class="a">
-<td align="left"><code>configurator</code></td>
+<td><code>configurator</code></td>
<td><code>@configurator <roleHint></code></td>
@@ -585,7 +585,7 @@
<tr class="b">
-<td align="left"><code>execute</code></td>
+<td><code>execute</code></td>
<td>
@@ -612,7 +612,7 @@
<tr class="a">
-<td align="left"><code>executionStrategy</code></td>
+<td><code>executionStrategy</code></td>
<td><code>@executionStrategy <strategy></code></td>
@@ -623,7 +623,7 @@
<tr class="b">
-<td align="left"><code>goal</code></td>
+<td><code>goal</code></td>
<td><code>@goal <goalName></code></td>
@@ -635,7 +635,7 @@
<tr class="a">
-<td align="left"><code>inheritByDefault</code></td>
+<td><code>inheritByDefault</code></td>
<td><code>@inheritByDefault <true|false></code></td>
@@ -646,7 +646,7 @@
<tr class="b">
-<td align="left"><code>instantiationStrategy</code></td>
+<td><code>instantiationStrategy</code></td>
<td><code>@instantiationStrategy <per-lookup></code></td>
@@ -657,7 +657,7 @@
<tr class="a">
-<td align="left"><code>phase</code></td>
+<td><code>phase</code></td>
<td><code>@phase <phaseName></code></td>
@@ -673,7 +673,7 @@
<tr class="b">
-<td align="left"><code>requiresDependencyResolution</code></td>
+<td><code>requiresDependencyResolution</code></td>
<td><code>@requiresDependencyResolution <requiredClassPath></code></td>
@@ -684,11 +684,11 @@
execute. The matrix below illustrates which values for <i><requiredClassPath></i> (first column) are
supported and which dependency scopes (first row) they will request to resolve:
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<tr class="a">
-<td align="left"></td>
+<td></td>
<td>system</td>
@@ -703,7 +703,7 @@
<tr class="b">
-<td align="left"><code>compile</code></td>
+<td><code>compile</code></td>
<td>X</td>
@@ -718,7 +718,7 @@
<tr class="a">
-<td align="left"><code>runtime</code></td>
+<td><code>runtime</code></td>
<td>-</td>
@@ -733,7 +733,7 @@
<tr class="b">
-<td align="left"><code>compile+runtime</code> (since Maven 3.0)</td>
+<td><code>compile+runtime</code> (since Maven 3.0)</td>
<td>X</td>
@@ -748,7 +748,7 @@
<tr class="a">
-<td align="left"><code>test</code></td>
+<td><code>test</code></td>
<td>X</td>
@@ -769,7 +769,7 @@
<tr class="a">
-<td align="left"><code>requiresDependencyCollection</code></td>
+<td><code>requiresDependencyCollection</code></td>
<td><code>@requiresDependencyCollection <requiredClassPath></code></td>
@@ -790,7 +790,7 @@
<tr class="b">
-<td align="left"><code>requiresDirectInvocation</code></td>
+<td><code>requiresDirectInvocation</code></td>
<td><code>@requiresDirectInvocation <true|false></code></td>
@@ -801,7 +801,7 @@
<tr class="a">
-<td align="left"><code>requiresOnline</code></td>
+<td><code>requiresOnline</code></td>
<td><code>@requiresOnline <true|false></code></td>
@@ -812,7 +812,7 @@
<tr class="b">
-<td align="left"><code>requiresProject</code></td>
+<td><code>requiresProject</code></td>
<td><code>@requiresProject <true|false></code></td>
@@ -823,7 +823,7 @@
<tr class="a">
-<td align="left"><code>requiresReports</code></td>
+<td><code>requiresReports</code></td>
<td><code>@requiresReports <true|false></code></td>
@@ -834,7 +834,7 @@
<tr class="b">
-<td align="left"><code>threadSafe</code></td>
+<td><code>threadSafe</code></td>
<td><code>@threadSafe <true|false></code></td>
@@ -852,7 +852,7 @@
<tr class="a">
-<td align="left"><code>description</code></td>
+<td><code>description</code></td>
<td>none (detected)</td>
@@ -867,7 +867,7 @@
<tr class="b">
-<td align="left"><code>implementation</code></td>
+<td><code>implementation</code></td>
<td>none (detected)</td>
@@ -878,7 +878,7 @@
<tr class="a">
-<td align="left"><code>language</code></td>
+<td><code>language</code></td>
<td>none (detected)</td>
@@ -891,7 +891,7 @@
<tr class="b">
-<td align="left"><code>deprecated</code></td>
+<td><code>deprecated</code></td>
<td><code>@deprecated <deprecated-text></code></td>
@@ -904,7 +904,7 @@
<tr class="a">
-<td align="left"><code>since</code></td>
+<td><code>since</code></td>
<td><code>@since <since-text></code></td>
@@ -935,7 +935,7 @@
<p>Each parameter for a Mojo must be specified in the
plugin descriptor as follows:</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<tr class="a">
@@ -951,7 +951,7 @@
<tr class="b">
-<td align="left"><code>alias</code></td>
+<td><code>alias</code></td>
<td><code>@parameter alias="myAlias"</code></td>
@@ -964,7 +964,7 @@
<tr class="a">
-<td align="left"><code>configuration</code></td>
+<td><code>configuration</code></td>
<td><code>@component role="..." roleHint="..."</code></td>
@@ -983,7 +983,7 @@
<tr class="b">
-<td align="left"><code>configuration</code></td>
+<td><code>configuration</code></td>
<td>maven-plugin-plugin 2.x:<br /><code>@parameter expression="${aSystemProperty}"
default-value="${anExpression}"</code><br /><br />
@@ -1015,7 +1015,7 @@
<tr class="a">
-<td align="left"><code>editable</code></td>
+<td><code>editable</code></td>
<td><code>@readonly</code></td>
@@ -1035,7 +1035,7 @@
<tr class="b">
-<td align="left"><code>required</code></td>
+<td><code>required</code></td>
<td><code>@required</code></td>
@@ -1052,7 +1052,7 @@
<tr class="a">
-<td align="left"><code>description</code></td>
+<td><code>description</code></td>
<td>none (detected)</td>
@@ -1067,7 +1067,7 @@
<tr class="b">
-<td align="left"><code>name</code></td>
+<td><code>name</code></td>
<td>none (detected)</td>
@@ -1081,7 +1081,7 @@
<tr class="a">
-<td align="left"><code>type</code></td>
+<td><code>type</code></td>
<td>none (detected)</td>
@@ -1098,7 +1098,7 @@
<tr class="b">
-<td align="left"><code>deprecated</code></td>
+<td><code>deprecated</code></td>
<td><code>@deprecated <deprecated-text></code></td>
@@ -1111,7 +1111,7 @@
<tr class="a">
-<td align="left"><code>since</code></td>
+<td><code>since</code></td>
<td><code>@since <since-text></code></td>
@@ -1134,7 +1134,7 @@
</p>
</section>
<section>
-<h1><a name="Plugin_Tools"></a>Plugin Tools</h1>
+<h1>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
@@ -1150,14 +1150,14 @@
create plugin artifacts.</p>
</section>
<section>
-<h1><a name="Project_Descriptor_.28POM.29_Requirements"></a>Project Descriptor (POM) Requirements</h1>
+<h1>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
for script-based plugins. The following details the POM elements
which are necessary to build a Maven plugin artifact.</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<tr class="a">
@@ -1172,7 +1172,7 @@
<tr class="b">
-<td align="left">packaging</td>
+<td>packaging</td>
<td>Yes</td>
@@ -1188,7 +1188,7 @@
<tr class="a">
-<td align="left">scriptSourceDirectory</td>
+<td>scriptSourceDirectory</td>
<td>No</td>
@@ -1220,7 +1220,7 @@
</p>
</section>
<section>
-<h1><a name="IDE_integration"></a>IDE integration</h1>
+<h1>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
@@ -1246,7 +1246,7 @@
</ol>
</section>
<section>
-<h1><a name="Resources"></a>Resources</h1>
+<h1>Resources</h1>
<p>This section simply gives a listing of pointers for more
information.</p>
Modified: maven/website/content/developers/release/index.html
==============================================================================
--- maven/website/content/developers/release/index.html (original)
+++ maven/website/content/developers/release/index.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/developers/release/index.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/release/index.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<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>
-<h1><a name="Releasing_A_Maven_Project"></a>Releasing A Maven Project</h1>
+<h1>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>
Modified: maven/website/content/developers/release/maven-core-release.html
==============================================================================
--- maven/website/content/developers/release/maven-core-release.html (original)
+++ maven/website/content/developers/release/maven-core-release.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/developers/release/maven-core-release.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/release/maven-core-release.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Releasing Maven</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../../css/site.css" />
@@ -138,7 +138,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section><section>
-<h2><a name="Releasing_Maven"></a>Releasing Maven</h2><!--
+<h2>Releasing Maven</h2><!--
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
@@ -182,7 +182,7 @@ under the License.
version. The tag that produced the failed released is left in place for
posterity. So if the release of, say, 3.2.4 fails then we move forward
with 3.2.5.</p><section>
-<h3><a name="Produce_Release_Candidates"></a>Produce Release Candidates</h3>
+<h3>Produce Release Candidates</h3>
<p>For non-alpha/beta releases, release candidates are produced before the actual release.</p>
<p>Checkout <a href="https://dist.apache.org/repos/dist/dev/maven/maven-3" class="externalLink">https://dist.apache.org/repos/dist/dev/maven/maven-3</a> then create the necessary directory tree.</p>
<p>Copy the binaries and src-tar.gz with their sha512/asc to the created directories.</p>
@@ -195,14 +195,14 @@ with 3.2.5.</p><section>
<p>After producing the RC, request that the developers test the release on the list. If a regression is found, a new release candidate is rolled.</p>
<p>After a reasonable time without regressions found, a wider audience may be polled if the release manager desires (for example, users@).</p>
<p>Once happy with a release candidate, the full release is performed, with the final version in place.</p></section><section>
-<h3><a name="Produce_the_Release"></a>Produce the Release</h3>
+<h3>Produce the Release</h3>
<p>To produce a final release, the same process as for standard projects is followed:</p>
<ul>
<li><a href="./maven-project-release-procedure.html">Maven Project Common Release Procedure</a></li>
</ul>
<p>Below describes the additional steps that need to be taken at the points where the website are updated in those instructions.</p><section>
-<h4><a name="Prepare_the_Release_Notes"></a>Prepare the Release Notes</h4>
+<h4>Prepare the Release Notes</h4>
<p>Checkout Maven site source <a href="https://github.com/apache/maven-site.git" class="externalLink">https://github.com/apache/maven-site.git</a>.</p>
<p>Create the release notes:</p>
<ul>
@@ -210,7 +210,7 @@ with 3.2.5.</p><section>
<li>create <code>content/markdown/docs/$version</code></li>
<li>create <code>content/markdown/docs/$version/release-notes.md</code> (see other versions for an example)</li>
</ul></section><section>
-<h4><a name="Stage_the_Latest_Documentation"></a>Stage the Latest Documentation</h4>
+<h4>Stage the Latest Documentation</h4>
<p>Once the release is prepared, but before the release vote, the site needs to be staged.</p>
<p>From the release checkout, stage the site:</p>
@@ -218,35 +218,35 @@ with 3.2.5.</p><section>
mvn scm-publish:publish-scm
</code></pre></div>
<p>This will publish the Maven core site in <a href="/ref/3-LATEST">/ref/3-LATEST</a>.</p></section></section><section>
-<h3><a name="Complete_the_release"></a>Complete the release</h3>
+<h3>Complete the release</h3>
<p>After a successful vote you should do the following steps to finish the release.</p><section>
-<h4><a name="Add_New_Version_to_ASF_Distribution_Directory"></a>Add New Version to ASF Distribution Directory</h4>
+<h4>Add New Version to ASF Distribution Directory</h4>
<p>In addition to promoting the repository, the release archives should be
moved to the release svnpubsub tree:</p>
<div class="source"><pre class="prettyprint linenums"><code>svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Publish Maven $VERSION Distribution Archives"
</code></pre></div></section><section>
-<h4><a name="Update_the_DOAP_Information"></a>Update the DOAP Information</h4>
+<h4>Update the DOAP Information</h4>
<p>Edit <a href="https://github.com/apache/maven/blob/master/doap_Maven.rdf" class="externalLink">https://github.com/apache/maven/blob/master/doap_Maven.rdf</a> to list the new release.</p></section><section>
-<h4><a name="Update_the_Web_Site"></a>Update the Web Site</h4>
+<h4>Update the Web Site</h4>
<p>Checkout Maven site source <a href="https://github.com/apache/maven-site.git" class="externalLink">https://github.com/apache/maven-site.git</a>.</p>
<p>For 3.x: update the <code>versions3x</code>, <code>currentStableVersion</code> and <code>currentStableReleaseDate</code> properties in <code>pom.xml</code></p>
<p>Next, update release history <code>content/markdown/docs/history.md.vm</code>.</p>
<p>Only deploy the site once the release is present on the mirrors, and the reference documentation has been deployed to <a href="/ref">/ref/</a>.</p></section><section>
-<h4><a name="Deploy_the_Latest_Documentation_to_Target_Versioned_Location"></a>Deploy the Latest Documentation to Target Versioned Location</h4>
+<h4>Deploy the Latest Documentation to Target Versioned Location</h4>
<p>The reference documentation for Maven core source code references and API docs has been staged in a previous step: now it needs to be deployed to its dedicated directory before deploying the web site pointing to the new version.</p>
<p>This consists in copying in website svn tree the staging /ref/3-LATEST directory to final /ref/<code>$VERSION</code>.</p>
<div class="source"><pre class="prettyprint linenums"><code>svn cp https://svn.apache.org/repos/asf/maven/website/components/ref/3-LATEST https://svn.apache.org/repos/asf/maven/website/components/ref/$VERSION -m "Maven $VERSION released"
</code></pre></div></section></section><section>
-<h3><a name="Information_on_.2Fref.2Fcurrent_mechanism"></a>Information on <code>/ref/current</code> mechanism</h3>
+<h3>Information on <code>/ref/current</code> mechanism</h3>
<p>The redirection from <code>/ref/current</code> to actual Maven version reference is done through <code>.htaccess</code> published in site.</p><section>
-<h4><a name="Deploying_the_Release_Website"></a>Deploying the Release Website</h4>
+<h4>Deploying the Release Website</h4>
<p>Once both of the above have synced to the main site and a suitable number of mirrors, proceed to update the web site and produce the announcement.</p>
<p>Commit your changes and then <a href="../website/deploy-maven-website.html">deploy the main Maven site</a>.</p></section><section>
-<h4><a name="Remove_Old_Versions_from_ASF_Distribution_Directory"></a>Remove Old Versions from ASF Distribution Directory</h4>
+<h4>Remove Old Versions from ASF Distribution Directory</h4>
<p>Next, any superseded releases should be removed from the above locations (after confirming that they exist in /www/archive.apache.org/dist/maven).</p></section><section>
-<h4><a name="Proceed_with_Announcement"></a>Proceed with Announcement</h4>
+<h4>Proceed with Announcement</h4>
<p>You can now proceed with the steps outlined after deploying the website on <a href="./maven-project-release-procedure.html">Maven Project Common Release Procedure</a></p></section></section></section></section>
</main>
</div>