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 sl...@apache.org on 2023/02/09 00:34:07 UTC
svn commit: r1907531 [3/25] - 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/developers/index.html
==============================================================================
--- maven/website/content/developers/index.html (original)
+++ maven/website/content/developers/index.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/index.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/index.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,8 +10,7 @@
<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-M4" />
- <meta name="author" content="Vincent Siveton
-Brett Porter" />
+ <meta name="author" content="Vincent Siveton, Brett Porter" />
<meta name="date" content="2015-02-14" />
<title>Maven – Maven Developer Centre</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
@@ -49,8 +48,8 @@ Brett Porter" />
<ul class="breadcrumb">
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
- <li class="active ">Maven Developer Centre <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/index.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li class="active ">Maven Developer Centre <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/index.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
@@ -134,47 +133,101 @@ Brett Porter" />
</div>
</header>
<main id="bodyColumn" class="span10" >
-<section>
-<h1>Maven Developer Centre</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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<section><section>
+<h2>Maven Developer Centre</h2>
<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>Contributors Resources</h2>
+<p>If you cannot find your answers here, feel free to ask the <a href="mailto:dev@maven.apache.org" class="externalLink">Maven Developer List</a>.</p><section>
+<h3>Contributors Resources</h3>
+<ul>
+
+<li>
+<p><a href="../guides/development/guide-helping.html">Guide to helping with Maven</a></p></li>
+<li>
+<p><a href="../guides/development/guide-maven-development.html">Developing Maven</a></p></li>
+<li>
+<p><a href="../guides/development/guide-building-maven.html">Building Maven</a></p></li>
+<li>
+<p><a href="../scm.html">Source Code</a></p></li>
+<li>
+<p><a href="https://ci-maven.apache.org/job/Maven/job/maven-box/" class="externalLink">Continuous Integration</a></p></li>
+<li>
+<p><a href="../plugin-developers/common-bugs.html">Common Bugs and Pitfalls</a></p></li>
+<li>
+<p><a href="../project-roles.html">Apache Maven Project Roles</a></p></li>
+</ul></section><section>
+<h3>Committers Resources</h3><section>
+<h4>General Resources</h4>
<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>
-<li><a href="../guides/development/guide-building-maven.html">Building Maven</a></li>
-<li><a href="../scm.html">Source Code</a></li>
-<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>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>
-<li><a href="./committer-settings.html">Committer Settings</a></li>
-<li><a href="./retirement-plan-plugins.html">Retirement Plan for Plugins</a></li>
-<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>Developers Conventions</h2>
+
+<li>
+<p><a href="./welcome-to-new-committers.html">Guide for new Maven committers</a></p></li>
+<li>
+<p><a href="./committer-environment.html">Committer Environment</a></p></li>
+<li>
+<p><a href="./committer-settings.html">Committer Settings</a></p></li>
+<li>
+<p><a href="./retirement-plan-plugins.html">Retirement Plan for Plugins</a></p></li>
+<li>
+<p><a href="./dependency-policies.html">Maven Dependency Policies</a></p></li>
+<li>
+<p><a href="./compatibility-plan.html">Maven Plugins and Components Compatibility Plan</a></p></li>
+<li>
+<p><a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=5964567" class="externalLink">Maven Proposals/Backlog</a></p></li>
+</ul></section></section><section>
+<h3>Developers Conventions</h3>
<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>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>Maven Website</h2>
+
+<li>
+<p><a href="./conventions/code.html">Maven Code Style And Conventions</a></p></li>
+<li>
+<p><a href="./conventions/jira.html">Maven JIRA Convention</a></p></li>
+<li>
+<p><a href="./conventions/git.html">Maven Git Convention</a></p></li>
+</ul>
+<p><strong>Note</strong>: If you cannot find your answers here, feel free to ask the <a href="mailto:dev@maven.apache.org" class="externalLink">Maven Developer List</a>.</p></section><section>
+<h3>Making Releases</h3>
+<ul>
+
+<li>
+<p><a href="./release/pmc-gpg-keys.html">Making GPG Keys</a></p></li>
+<li>
+<p><a href="./release/index.html">Release Process</a></p></li>
+</ul></section><section>
+<h3>Maven Website</h3>
<ul>
-<li><a href="./website/index.html">Deploy Maven Website</a></li></ul></section><section>
-<h2>Other Resources</h2>
+
+<li><a href="./website/index.html">Deploy Maven Website</a></li>
+</ul></section><section>
+<h3>Other Resources</h3>
<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>
+
+<li>
+<p><a href="https://www.apache.org/dev/" class="externalLink">ASF Development Infrastructure Information</a></p></li>
+<li>
+<p><a href="https://www.apache.org/foundation/" class="externalLink">About the Apache Software Foundation</a></p></li>
+</ul><!-- TODO: tasks as buttons? -->
+<!-- TODO: de-dupe with existing documents in community -->
+<!-- TODO: clean up, have cookbook with more in depth documents like cutting releases, etc. -->
+</section></section></section>
</main>
</div>
</div>
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 Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 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-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,7 +48,7 @@
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class="active ">Mojo API Specification <a href="https://github.com/apache/maven-site/tree/master/content/xdoc/developers/mojo-api-specification.xml"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
Modified: maven/website/content/developers/release/index.html
==============================================================================
--- maven/website/content/developers/release/index.html (original)
+++ maven/website/content/developers/release/index.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/release/index.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/release/index.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,8 +48,8 @@
<ul class="breadcrumb">
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
- <li class="active ">Releasing A Maven Project <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/release/index.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li class="active ">Releasing A Maven Project <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/release/index.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../../download.cgi" title="Download">Download</a></li>
@@ -139,16 +139,42 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<section>
-<h1>Releasing A Maven Project</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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<section><section>
+<h2>Releasing A Maven Project</h2>
<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>
+<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><!-- nothing specific: normal component * {{{./maven-plugin-release.html} Releasing a Maven plugin project}} -->
+<!-- nothing specific: normal component * {{{./maven-shared-release.html} Releasing a Maven shared component or subproject}} -->
+
<ul>
-<li><a href="./maven-core-release.html"> Releasing Maven Core</a></li>
-<li><a href="./parent-pom-release.html"> Releasing a parent POM</a></li></ul>
+
+<li>
+<p><a href="./maven-core-release.html">Releasing Maven Core</a></p></li>
+<li>
+<p><a href="./parent-pom-release.html">Releasing a parent POM</a></p></li>
+</ul>
<p>The above links all provide specific information for those types of releases, but they all refer back to the common documentation:</p>
<ul>
-<li><a href="./maven-project-release-procedure.html"> Maven Project Common Release procedure</a></li></ul></section>
+
+<li><a href="./maven-project-release-procedure.html">Maven Project Common Release procedure</a></li>
+</ul></section></section>
</main>
</div>
</div>
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 Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 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-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -47,7 +47,7 @@
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class="active ">Releasing Maven <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/release/maven-core-release.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../../download.cgi" title="Download">Download</a></li>
Modified: maven/website/content/developers/release/maven-project-release-procedure.html
==============================================================================
--- maven/website/content/developers/release/maven-project-release-procedure.html (original)
+++ maven/website/content/developers/release/maven-project-release-procedure.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/release/maven-project-release-procedure.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/release/maven-project-release-procedure.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,8 +10,7 @@
<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-M4" />
- <meta name="author" content="Jason van Zyl
-Karl Heinz Marbaise" />
+ <meta name="author" content="Jason van Zyl, Karl Heinz Marbaise" />
<meta name="date" content="2018-04-07" />
<title>Maven – Releasing A Maven Project</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
@@ -49,8 +48,8 @@ Karl Heinz Marbaise" />
<ul class="breadcrumb">
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
- <li class="active ">Releasing A Maven Project <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/release/maven-project-release-procedure.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li class="active ">Releasing A Maven Project <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/release/maven-project-release-procedure.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../../download.cgi" title="Download">Download</a></li>
@@ -140,36 +139,65 @@ Karl Heinz Marbaise" />
</div>
</header>
<main id="bodyColumn" class="span10" >
-<section>
-<h1>Performing a Maven Project Release</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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<section><section>
+<h2>Performing a Maven Project Release</h2>
<p>This document covers the common release procedures used by the Maven team to perform releases.</p><section>
-<h2><a id="Prerequisites">Prerequisites</a></h2>
+<h3>Prerequisites</h3>
<p>Be sure that:</p>
<ul>
-<li>you have a recent Git client installed and on your shell's path.</li>
-<li>you have JDK 8 installed and on your shell's path to build Maven 3.7.0+. Details about minimum JDK version to build an appropriate version can be found here: <a href="/docs/history.html">https://maven.apache.org/docs/history.html</a></li>
-<li>if you receive an OutOfMemoryError during the build, make sure to have set the environment variable <code>MAVEN_OPTS=-Xmx512m</code></li>
-<li>you must use Maven 3.3.9+.</li>
-<li>follow Apache environment configuration steps outlined at: <a class="externalLink" href="https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing Maven Artifacts</a>.</li></ul></section><section>
-<h2>Before you begin</h2>
+
+<li>
+<p>you have a recent Git client installed and on your shell's path.</p></li>
+<li>
+<p>you have JDK 8 installed and on your shell's path to build Maven 3.7.0+. Details about minimum JDK version to build an appropriate version can be found here: <a href="/docs/history.html">https://maven.apache.org/docs/history.html</a></p></li>
+<li>
+<p>if you receive an OutOfMemoryError during the build, make sure to have set the environment variable <code>MAVEN_OPTS\=-Xmx512m</code></p></li>
+<li>
+<p>you must use Maven 3.3.9+.</p></li>
+<li>
+<p>follow Apache environment configuration steps outlined at: <a href="https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env" class="externalLink">Publishing Maven Artifacts</a>.</p></li>
+</ul></section><section>
+<h3>Before you begin</h3>
<p>If you started here, you may first want to review one of the following documents that cover the specifics of various types of releases we have in the Maven Project:</p>
<ul>
-<li><a href="./maven-core-release.html"> Releasing Maven Core</a></li>
-<li><a href="./parent-pom-release.html"> Releasing a parent POM</a></li></ul></section><section>
-<h2>Consider updating the parent versions</h2>
+
+<li>
+<p><a href="./maven-core-release.html">Releasing Maven Core</a></p></li>
+<li>
+<p><a href="./parent-pom-release.html">Releasing a parent POM</a></p></li>
+</ul></section><section>
+<h3>Consider updating the parent versions</h3>
<p>If the item you are planning to release is not using the most recent version of its parent (see <a href="../../pom/">parent POMs</a> index), consider taking this opportunity to update to it.</p></section><section>
-<h2>Make sure that site compilation works</h2>
+<h3>Make sure that site compilation works</h3>
<p>Particularly if you update the parent or if you updated your javadoc, the site compilation process may fail, or reveal a conspicuous error. It is stressful and time-consuming to discover this *after* you stage a release and then try to follow the procedure to deploy the site for review. So you may find it more pleasant to check out the state of the site before you start:</p>
-<div>
-<pre>mvn -Preporting site site:stage</pre></div></section><section>
-<h2>Stage the Release</h2>
-<ol style="list-style-type: decimal">
-<li>Follow the release preparation, staging and closing the repository steps outlined in <a class="externalLink" href="https://infra.apache.org/publishing-maven-artifacts.html">Publishing Maven Releases</a>. </li>
-<li>Stage the latest documentation as explained in <a href="../website/deploy-component-reference-documentation.html">deploying Maven components reference documentation</a>.</li></ol></section><section>
-<h2>Call the vote</h2>
+
+<div class="source"><pre class="prettyprint linenums"><code>mvn -Preporting site site:stage
+</code></pre></div></section><section>
+<h3>Stage the Release</h3>
+<p>1 Follow the release preparation, staging and closing the repository steps outlined in <a href="https://infra.apache.org/publishing-maven-artifacts.html" class="externalLink">Publishing Maven Releases</a>.</p>
+<p>1 Stage the latest documentation as explained in <a href="../website/deploy-component-reference-documentation.html">deploying Maven components reference documentation</a>.</p></section><section>
+<h3>Call the vote</h3>
<p>Propose a vote on the dev list with the closed issues, the issues left, the staging repository and the staging site. For instance:</p>
-<div>
-<pre>To: "Maven Developers List" <dev@maven.apache.org>
+
+<div class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
Subject: [VOTE] Release Apache Maven XXX Plugin version Y.Z
Hi,
@@ -198,25 +226,27 @@ Vote open for at least 72 hours.
[ ] +1
[ ] +0
[ ] -1
-</pre></div>
-<p>To get the JIRA release notes link, browse to the plugin's or component's JIRA page, select the <i>Road Map</i> link, and use the link to <i>Release Notes</i> that is next to the version being released.</p>
-<p>To get the list of issues left in JIRA, browse to the plugin's or component's JIRA page, and from the <i>Preset Filters</i> on the right, use the link for <i>Outstanding</i> issues.</p>
+
+</code></pre></div>
+<p>To get the JIRA release notes link, browse to the plugin's or component's JIRA page, select the <em>Road Map</em> link, and use the link to <em>Release Notes</em> that is next to the version being released.</p>
+<p>To get the list of issues left in JIRA, browse to the plugin's or component's JIRA page, and from the <em>Preset Filters</em> on the right, use the link for <em>Outstanding</em> issues.</p>
<p>The vote is open for at least 72 hours means, that you need to wait at least 72 hours before proceeding. This gives others time to test your release and check that everything is good. If you have received after that not enough +1 votes to reach the quorum, this doesn't mean, the vote failed. It just takes a bit longer.</p></section><section>
-<h2>Check the vote results</h2>
-<p>Copied from <a class="externalLink" href="https://www.apache.org/foundation/voting.html#ReleaseVotes">Votes on Package Releases</a>.</p>
-<div>
-<pre>Votes on whether a package is ready to be released use majority approval
+<h3>Check the vote results</h3>
+<p>Copied from <a href="https://www.apache.org/foundation/voting.html#ReleaseVotes" class="externalLink">Votes on Package Releases</a>.</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>Votes on whether a package is ready to be released use majority approval
-- i.e. at least three PMC members must vote affirmatively for release,
and there must be more positive than negative votes. Releases may not be vetoed.
Generally the community will cancel the release vote if anyone identifies serious problems,
but in most cases the ultimate decision, lies with the individual serving as release manager.
The specifics of the process may vary from project to project,
-but the 'minimum quorum of three +1 votes' rule is universal.</pre></div>
-<p>The list of PMC members is available at <a class="externalLink" href="https://people.apache.org/committers-by-project.html#maven-pmc">https://people.apache.org/committers-by-project.html#maven-pmc</a>.</p><section>
-<h3>Successful vote</h3>
-<p>Once a vote is <b>successful</b>, post the result to the <code>dev</code> list and cc the <code>PMC</code>. For instance:</p>
-<div>
-<pre>To: "Maven Developers List" <dev@maven.apache.org>
+but the 'minimum quorum of three +1 votes' rule is universal.
+</code></pre></div>
+<p>The list of PMC members is available at <a href="https://people.apache.org/committers-by-project.html#maven-pmc" class="externalLink">https://people.apache.org/committers-by-project.html#maven-pmc</a>.</p><section>
+<h4>Successful vote</h4>
+<p>Once a vote is <strong>successful</strong>, post the result to the <code>dev</code> list and cc the <code>PMC</code>. For instance:</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
CC: "Maven Project Management Committee List" <private@maven.apache.org>
Subject: [RESULT] [VOTE] Release Apache Maven XXX Plugin version Y.Z
@@ -228,63 +258,77 @@ The vote has passed with the following r
PMC quorum: ...
-I will promote the source release zip file to Apache distribution area and the artifacts to the central repo.</pre></div>
+I will promote the source release zip file to Apache distribution area and the artifacts to the central repo.
+</code></pre></div>
<p>Follow the procedure to the end.</p></section><section>
-<h3>Unsuccessful vote</h3>
-<p>Once a vote is <b>unsuccessful</b>, post the result to the <code>dev</code> list, For instance:</p>
-<div>
-<pre>To: "Maven Developers List" <dev@maven.apache.org>
+<h4>Unsuccessful vote</h4>
+<p>Once a vote is <strong>unsuccessful</strong>, post the result to the <code>dev</code> list, For instance:</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
Subject: [CANCEL] [VOTE] Release Apache Maven XXX Plugin version Y.Z
Hi,
-The vote has been canceled.</pre></div>
+The vote has been canceled.
+</code></pre></div>
<p>For canceled vote the process will need to be restarted.</p>
<p>Be sure to:</p>
<ul>
-<li>drop your staging repository as described in <a class="externalLink" href="https://www.apache.org/dev/publishing-maven-artifacts.html">Drop a repository</a></li>
-<li>create new version for next round <code>Y.Z+1</code></li>
-<li>assign issues from version <code>Y.Z</code> also to version <code>Y.Z+1</code></li>
-<li>mark the <code>Y.Z</code> version as <b>archived</b></li>
-<li>report found issues and assign them to version <code>Y.Z+1</code></li>
-<li>fix found issues</li></ul>
-<p>Start the process for version <code>Y.Z+1</code> from the beginning.</p></section></section><section>
-<h2>Copy the source release to the Apache Distribution Area</h2>
-<p>The official Apache release is the 'source-release' bundle distributed in <code>www.apache.org/dist</code>, as described in <a class="externalLink" href="https://www.apache.org/dev/release-distribution">Apache Release Distribution Policy</a>. All releases for Maven must be copied to <a class="externalLink" href="https://www.apache.org/dist/maven/">the official Maven release area</a>.</p>
-<p>The release area is maintained with svnpubsub. To deliver a release, you add it to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven">the subversion repository for the dist area</a>: add the release, its signature and sha512 checksum files, copying them from <code>target/checkout/target/</code> directory created during <code>mvn release:perform</code> step. Currently this requires to be in maven-pmc group (see <a class="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">INFRA-5945</a>). If you are not a PMC member, drop a line to <i>private@maven.apache.org</i> and ask them to do this step (and the next one) for you: the PMC member will get the source release bundle and its signature from Nexus staging repository and will create sha512 checksum file by hand, for example using shell:</p>
-<div>
-<pre>for f in *.zip ; do echo -n $(sha512sum $f | cut -c -128) > $f.sha512 ; done</pre></div>
+
+<li>
+<p>drop your staging repository as described in <a href="https://www.apache.org/dev/publishing-maven-artifacts.html" class="externalLink">Drop a repository</a></p></li>
+<li>
+<p>create new version for next round <code>Y.Z\+1</code></p></li>
+<li>
+<p>assign issues from version <code>Y.Z</code> also to version <code>Y.Z\+1</code></p></li>
+<li>
+<p>mark the <code>Y.Z</code> version as <strong>archived</strong></p></li>
+<li>
+<p>report found issues and assign them to version <code>Y.Z\+1</code></p></li>
+<li>
+<p>fix found issues</p></li>
+</ul>
+<p>Start the process for version <code>Y.Z\+1</code> from the beginning.</p></section></section><section>
+<h3>Copy the source release to the Apache Distribution Area</h3>
+<p>The official Apache release is the ‘source-release’ bundle distributed in <code>www.apache.org/dist</code>, as described in <a href="https://www.apache.org/dev/release-distribution" class="externalLink">Apache Release Distribution Policy</a>. All releases for Maven must be copied to <a href="https://www.apache.org/dist/maven/" class="externalLink">the official Maven release area</a>.</p>
+<p>The release area is maintained with svnpubsub. To deliver a release, you add it to <a href="https://dist.apache.org/repos/dist/release/maven" class="externalLink">the subversion repository for the dist area</a>: add the release, its signature and sha512 checksum files, copying them from <code>target/checkout/target/</code> directory created during <code>mvn release:perform</code> step. Currently this requires to be in maven-pmc group (see <a href="https://issues.apache.org/jira/browse/INFRA-5945" class="externalLink">INFRA-5945</a>). If you are not a PMC member, drop a line to <em><a href="mailto:private@maven.apache.org" class="externalLink">private@maven.apache.org</a></em> and ask them to do this step (and the next one) for you: the PMC member will get the source release bundle and its signature from Nexus staging repository and will create sha512 checksum file by hand, for example using shell:</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>for f in *.zip ; do echo -n $(sha512sum $f | cut -c -128) > $f.sha512 ; done
+</code></pre></div>
<p>For example:</p>
-<div>
-<pre>wagon/wagon-2.2-source-release.zip
+
+<div class="source"><pre class="prettyprint linenums"><code>wagon/wagon-2.2-source-release.zip
wagon/wagon-2.2-source-release.zip.asc
-wagon/wagon-2.2-source-release.zip.sha512</pre></div>
-<p>You should also run 'svn rm' as needed to clear out older releases. As per <a class="externalLink" href="https://www.apache.org/legal/release-policy.html#where-do-releases-go">Apache Release Policy</a>, only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver will have copied it to the archive.</p>
-<p>To check that everything is ok in the dist area, dist-tool-plugin has been written and run once a day to produce <a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/">"Check Source Release" and "Check Errors" reports</a>.</p></section><section>
-<h2>Add the release for next board report</h2>
-<p>After committing the 3 source-release files, visit <a class="externalLink" href="https://reporter.apache.org/addrelease.html?maven">Apache Committee Report Helper</a> to add your release data with the Full Version Name and Date of Release. (You will receive an e-mail for it as well).</p>
-<p>If you are not a PMC member, drop a line to <i>private@maven.apache.org</i> and ask them to do this step for you if they did not do the update while adding to release area.</p></section><section>
-<h2>Promote the release</h2>
+wagon/wagon-2.2-source-release.zip.sha512
+</code></pre></div>
+<p>You should also run ‘svn rm’ as needed to clear out older releases. As per <a href="https://www.apache.org/legal/release-policy.html#where-do-releases-go" class="externalLink">Apache Release Policy</a>, only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver will have copied it to the archive.</p>
+<p>To check that everything is ok in the dist area, dist-tool-plugin has been written and run once a day to produce <a href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/" class="externalLink">“Check Source Release” and “Check Errors” reports</a>.</p></section><section>
+<h3>Add the release for next board report</h3>
+<p>After committing the 3 source-release files, visit <a href="https://reporter.apache.org/addrelease.html?maven" class="externalLink">Apache Committee Report Helper</a> to add your release data with the Full Version Name and Date of Release. (You will receive an e-mail for it as well).</p>
+<p>If you are not a PMC member, drop a line to <em><a href="mailto:private@maven.apache.org" class="externalLink">private@maven.apache.org</a></em> and ask them to do this step for you if they did not do the update while adding to release area.</p></section><section>
+<h3>Promote the release</h3>
<p>Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.</p>
-<ol style="list-style-type: decimal">
-<li>See <a class="externalLink" href="https://www.apache.org/dev/publishing-maven-artifacts.html#promote">Promoting a Repo</a> for details on promotion.</li>
-<li>Deploy the current website
+<p>1 See <a href="https://www.apache.org/dev/publishing-maven-artifacts.html#promote" class="externalLink">Promoting a Repo</a> for details on promotion.</p>
+<p>1 Deploy the current website</p>
<p>As above, deploy the web site if appropriate and update the project site for the new release: use <a href="../website/component-reference-documentation-helper.html">Component Reference Documentation Helper</a> to generate commands or see <a href="../website/deploy-component-reference-documentation.html#Publishing_versioned_component_reference_documentation">Publishing versioned component reference documentation</a> for explanations. Note that not all projects follow these conventions exactly.</p>
-<p>In case there's an overview table with version (e.g. <a href="/plugins/index.html">plugins</a> and <a href="/shared/index.html">shared</a>) you can directly edit it on the github page.</p></li>
-<li>Update the version tracking in JIRA
-<p>In the relevant project, go to Administration, then Versions. Mark the <code>Y.Z</code> version as 'released'. Create version <code>Y.Z+1</code>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p>
-<p>Note: Currently this requires to be in the maven-pmc group. So, if you don't see the Administration option in JIRA, kindly ask <i>private@maven.apache.org</i> to do this step for you.</p></li>
-<li>Wait for everything to sync
-<ol style="list-style-type: lower-alpha">
-<li>Sync to <a class="externalLink" href="https://repo.maven.apache.org/maven2/org/apache/maven/">Maven Central</a>
-<p>The sync into central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.</p></li>
-<li>Sync to Maven Website
-<p>If the project you are releasing doesn't yet use svnpubsub for site deployment, the deployment of the Maven website will <a class="externalLink" href="https://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></li>
-<li>Create an announcement.
+<p>In case there's an overview table with version (e.g. <a href="/plugins/index.html">plugins</a> and <a href="/shared/index.html">shared</a>) you can directly edit it on the github page.</p>
+<p>1 Update the version tracking in JIRA</p>
+<p>In the relevant project, go to Administration, then Versions. Mark the <code>Y.Z</code> version as ‘released’. Create version <code>Y.Z\+1</code>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p>
+<p>Note: Currently this requires to be in the maven-pmc group. So, if you don't see the Administration option in JIRA, kindly ask <em><a href="mailto:private@maven.apache.org" class="externalLink">private@maven.apache.org</a></em> to do this step for you.</p>
+<p>1 Wait for everything to sync</p>
+<p>a Sync to <a href="https://repo.maven.apache.org/maven2/org/apache/maven/" class="externalLink">Maven Central</a></p>
+
+<div class="source"><pre class="prettyprint linenums"><code>The sync into central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.
+</code></pre></div>
+<p>a Sync to Maven Website</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>If the project you are releasing doesn't yet use svnpubsub for site deployment, the deployment of the Maven website will [take an hour or so to sync](https://www.apache.org/dev/release-publishing.html#sync-delay).
+</code></pre></div>
+<p>1 Create an announcement.</p>
<p>Following instructions are done for plugins: if you are releasing anything else than a plugin, you should adapt email content to match what you are releasing.</p>
-<p><b>Note:</b> You must send this email from your apache email account, e.g. YOUR_APACHE_USERNAME@apache.org otherwise the email to <code>announce@maven.apache.org</code> will bounce.</p>
-<div>
-<pre>From: YOUR_APACHE_USERNAME@apache.org
+<p><strong>Note:</strong> You must send this email from your apache email account, e.g. <a href="mailto:YOUR_APACHE_USERNAME@apache.org" class="externalLink">YOUR_APACHE_USERNAME@apache.org</a> otherwise the email to <code>announce@maven.apache.org</code> will bounce.</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>From: YOUR_APACHE_USERNAME@apache.org
To: announce@maven.apache.org, users@maven.apache.org
Cc: dev@maven.apache.org
Subject: [ANN] Apache Maven XXX Plugin Y.Z Released
@@ -314,10 +358,11 @@ Release Notes - Maven XXX Plugin - Versi
Enjoy,
-The Apache Maven team
-</pre></div></li>
-<li>If releasing the Apache Parent POM, notify <code>release-discuss@apache.org</code>: Several projects follow this list, and should be made aware of changes to the common parent. This might also be a step to take if other shared resources are released, or if plugin releases are of particular interest to that group.
-<p>If releasing Maven Core, notify <code>announce@apache.org</code></p></li>
-<li>Celebrate :o)</li></ol></section></section>
+
+</code></pre></div>
+<p>1 If releasing the Apache Parent POM, notify <code>release-discuss@apache.org</code>: Several projects follow this list, and should be made aware of changes to the common parent. This might also be a step to take if other shared resources are released, or if plugin releases are of particular interest to that group.</p>
+<p>If releasing Maven Core, notify <code>announce@apache.org</code></p>
+<p>1 Celebrate :o)</p></section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/release/parent-pom-release.html
==============================================================================
--- maven/website/content/developers/release/parent-pom-release.html (original)
+++ maven/website/content/developers/release/parent-pom-release.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/release/parent-pom-release.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/release/parent-pom-release.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,8 +10,7 @@
<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-M4" />
- <meta name="author" content="Hervé Boutemy
-Dennis Lundberg" />
+ <meta name="author" content="Hervé Boutemy, Dennis Lundberg" />
<meta name="date" content="2013-12-07" />
<title>Maven – Releasing A Parent POM</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
@@ -49,8 +48,8 @@ Dennis Lundberg" />
<ul class="breadcrumb">
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
- <li class="active ">Releasing A Parent POM <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/release/parent-pom-release.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li class="active ">Releasing A Parent POM <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/release/parent-pom-release.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../../download.cgi" title="Download">Download</a></li>
@@ -140,16 +139,36 @@ Dennis Lundberg" />
</div>
</header>
<main id="bodyColumn" class="span10" >
-<section>
-<h1>Releasing A Parent POM</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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<section><section>
+<h2>Releasing A Parent POM</h2>
<p>Releasing a Parent POM is much the same as any other Maven project. The following guide walks through most of the steps:</p>
<ul>
-<li><a href="./maven-project-release-procedure.html"> Maven Project Common Release procedure</a></li></ul>
+
+<li><a href="./maven-project-release-procedure.html">Maven Project Common Release procedure</a></li>
+</ul>
<p>Note that Parent POMs have particular conventions for managing and deploying the documentation.</p><section>
-<h2>Rationale</h2>
+<h3>Rationale</h3>
<p>To be able to publish a documentation for the parent POM without affecting released <code>pom.xml</code> and <code>site.xml</code>, parent POM projects have a specific structure, with the addition of <code>site-pom.xml</code> and <code>src/site-docs</code> to provide <code>mvn -f site-pom.xml site</code> with useful documentation content:</p>
-<div>
-<pre>|-- pom.xml
+
+<div class="source"><pre class="prettyprint linenums"><code>|-- pom.xml
|-- site-pom.xml
`-- src
|-- site
@@ -157,24 +176,25 @@ Dennis Lundberg" />
`-- site-docs
|-- apt
| `-- index.apt
- `-- site.xml</pre></div>
+ `-- site.xml
+</code></pre></div>
<p>And the <code>index.apt</code> page not only contains instructions about the content of the parent POM, but it maintains a history of POM releases links and diffs.</p>
<p>Each specific step is done to maintain <code>site-pom.xml</code> and <code>index.apt</code> in sync with the release being released.</p></section><section>
-<h2>Stage the release</h2>
+<h3>Stage the release</h3>
<p>Before staging the release with usual procedure, you need to update <code>site-pom.xml</code> and <code>index.apt</code> to take the future release into account:</p>
-<ol style="list-style-type: decimal">
-<li>update <code>site-pom.xml</code> parent POM version to match the version being released,</li>
-<li>update <code>src/site-docs/index.apt.vm</code>: add a line in the history of <code>pom.xml</code> for the version being released, referring to the future git release tag and date.</li></ol>
+<p>1 update <code>site-pom.xml</code> parent POM version to match the version being released,</p>
+<p>1 update <code>src/site-docs/index.apt.vm</code>: add a line in the history of <code>pom.xml</code> for the version being released, referring to the future git release tag and date.</p>
<p>Once these modifications are done, you can follow <a href="../website/deploy-component-reference-documentation.html">standard component documentation staging steps</a>, taking care to use the <code>site-pom.xml</code> POM, with <code>mvn -f site-pom.xml ...</code> command, each time the parent POM's site is generated or published.</p>
<p>Then the only difference is with commands to stage the site:</p>
-<div>
-<pre>cd target/checkout
+
+<div class="source"><pre class="prettyprint linenums"><code>cd target/checkout
mvn -f site-pom.xml site
-mvn -f site-pom.xml scm-publish:publish-scm</pre></div></section><section>
-<h2>Call the vote</h2>
+mvn -f site-pom.xml scm-publish:publish-scm
+</code></pre></div></section><section>
+<h3>Call the vote</h3>
<p>In the vote, instead of providing links to JIRA, the parent POMs should include a link to the Git changes since the last release:</p>
-<div>
-<pre>...
+
+<div class="source"><pre class="prettyprint linenums"><code>...
Hi,
Changes since the last release:
@@ -185,7 +205,8 @@ or for Maven Projects Parent POM:
https://github.com/apache/maven-parent/compare/maven-parent-<VERSION-OF-PREVIOUS-RELEASE>...maven-parent-<VERSION-OF-CURRENT-RELEASE>
Staging repo:
-...</pre></div></section></section>
+...
+</code></pre></div></section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/release/pmc-gpg-keys.html
==============================================================================
--- maven/website/content/developers/release/pmc-gpg-keys.html (original)
+++ maven/website/content/developers/release/pmc-gpg-keys.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/release/pmc-gpg-keys.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/release/pmc-gpg-keys.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,8 +48,8 @@
<ul class="breadcrumb">
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
- <li class="active ">Developers centre - Making GPG Keys <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/release/pmc-gpg-keys.apt"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li class="active ">Developers centre - Making GPG Keys <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/release/pmc-gpg-keys.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../../download.cgi" title="Download">Download</a></li>
@@ -139,12 +139,30 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<section>
-<h1>Introduction</h1>
-<p>You need to add your GPG keys in <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/project/KEYS">https://svn.apache.org/repos/asf/maven/project/KEYS</a> before a release. Here are some useful <a class="externalLink" href="http://www.gnupg.org/">GnuPG</a> commands to generate your Keys.</p><section>
-<h2>gpg --gen-key</h2>
-<div>
-<pre>>gpg --gen-key
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<section><section>
+<h2>Introduction</h2>
+<p>You need to add your GPG keys in <a href="https://svn.apache.org/repos/asf/maven/project/KEYS" class="externalLink">https://svn.apache.org/repos/asf/maven/project/KEYS</a> before a release. Here are some useful <a href="http://www.gnupg.org/" class="externalLink">GnuPG</a> commands to generate your Keys.</p><section>
+<h3>gpg –gen-key</h3>
+
+<div class="source"><pre class="prettyprint linenums"><code>>gpg --gen-key
gpg (GnuPG) 1.4.5; Copyright (C) 2006 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
@@ -217,29 +235,32 @@ pub 1024D/07DDB702 2006-10-10
Key fingerprint = 71F6 F555 8A61 71C4 330D B868 84F4 D470 07DD B702
uid Vincent Siveton <vsiveton@apache.org>
sub 2048g/D2814A59 2006-10-10
-</pre></div></section><section>
-<h2>gpg --list-sigs && gpg --armor --export</h2>
-<div>
-<pre>>gpg --list-sigs "Vincent Siveton" && gpg --armor --export "Vincent Siveton"
+
+</code></pre></div></section><section>
+<h3>gpg –list-sigs && gpg –armor –export</h3>
+
+<div class="source"><pre class="prettyprint linenums"><code>>gpg --list-sigs "Vincent Siveton" && gpg --armor --export "Vincent Siveton"
pub 1024D/07DDB702 2006-10-10
uid Vincent Siveton <vsiveton@apache.org>
sig 3 07DDB702 2006-10-10 Vincent Siveton <vsiveton@apache.org>
sub 2048g/D2814A59 2006-10-10
sig 07DDB702 2006-10-10 Vincent Siveton <vsiveton@apache.org>
-</pre></div></section></section><section>
-<h1>Version: GnuPG v1.4.5 (MingW32)</h1></section><section>
-<h1>mQGiBEUrnAsRBACQDiYGc1IQmkENLO9iznBg8otGPEbzqQozT5tsip5mB30f6Mc/ uuLxJkLdna7Ul3goIXDtCeLJq38gHvruNtVNR6S+juJFkd5sLEH8UJ18PbKuo/9I KGlzjtCYUUDC48czRr0efhqd54NH8ydNdpaZ76NGPPYfpXtk7kKgH/nPiwCgxozK IG2frMuWIvdFafbqdAl7y/sD/1Csf0r9jtHEeXOuyhm8jCGrSwzLbHUGKPUQP37P ajECHoWp6HnvHEEEpgVl+UjfZvrcVhzUoP+3r5HAugqERfkzK8AWc7qjIRjf64kU sjvto31G2KYz17Y8K9y4LkRkUspu8uw903pKnW/QELg4vvPVaEYpVVIdS6+cUreu V0hOA/4tW7T/GpzSbQmjvnIRQ7GVHbQeXsANwrS6NmGYIxafN9P9dfHV+eUieTu6 rvMP9coOhTYyEKZksrXw2MmXx5SzgxsXT0g4wDXbwxPYFfIdGUzFMobnVXiZ3G8l JEl9cML0cg3ZL1SoDmVf2iG3e3Yxxsne4AE1SU+0bbq0t7rqALQlVmluY2VudCBT aXZldG9uIDx2c2l2ZXRvbkBhcGFjaGUub3JnPohgBBMRAgAgBQJFK5wLAhsDBgsJ CAcDAgQVAggDBBYCAwECHgECF4AACgkQhPTUcAfdtwLP3gCbB/V1afp8hzxgirCS d2r6zCkJQ2IAoLKD/RIkkerNintYzrubJliJKBsRuQINBEUrnBgQCAD1+Sx+sBDL 1XCDtxQGsrZmMnJJVK/w4TPa/8weJkuZ1GSpINOjInmqESuehvCLoOoyfcuDVXlR PUZhKZLPEKfJlFptGNK19oTO/CoQN+SJLwR41FoumsBaf1YSSRpAukyx2J6cUxqf uWrK/T8PmgDw4YzmY96tev//41eZ5tSOxpoUM8ypnTaShtS9pjgHijEG0b7wBqeU e1OGOiLHgKyjEJUmlT
aLm1SxJ84eq0uAvYb+rb/QoWWLpjvr2/mo1kzUvCPgo3fh kgOxCxsC9QD836Mi5HFK6CRYU3yAFu5+/jM+LJzELy3u7uMuOSP6yuiK8WXopdbN WHOiJQfdc2gTAAMFCADdljjAG7L+8de6JzsEduKErKqWlTEWa99n1knaGKzdUUOP WrKxwqgI6PAJbxOfG4vBdDa6M6+nySJDMybQsOCFyNx91/7jYkgkmv8Jkt8CTW4z P4HKlFYMAFpU95ftpTAAMAlr+t+nZRTHi94/VHMv4yLGzB/xapbzToHKuUt1Yqom Ncio5px7RVoicn13/i/GeY72fIdC2LRGo6PXlmmDQemoAnUw0RJoEtzapb0j/tWd BdAtQQX/Ks7qhk4aDDHGgO+CdHAB8PLHDpMpUX5Zc9JX1xhyJcS8d/LPUpXtt9WN eekqDpx+jNmySJr6os7rPAkjx6jDUvHPiuKdT4aviEkEGBECAAkFAkUrnBgCGwwA CgkQhPTUcAfdtwJL9ACgmLuDxE+oZaMhyFSmXWN0fM36Bd8AoLYrvwydB9+nNnhJ 85TjkMPTgjp9 =Hg4C -----END PGP PUBLIC KEY BLOCK----- ----------------</h1>
-<p>You need to append this result to <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/project/KEYS">https://svn.apache.org/repos/asf/maven/project/KEYS</a>.</p>
-<p>You also need to upload your key to the public server: <a class="externalLink" href="http://pgp.mit.edu/">http://pgp.mit.edu/</a> by copying the same you appended in the text field and submit. You can ensure by searching your email in key search engine.</p><section>
-<h2>gpg --fingerprint</h2>
-<div>
-<pre>>gpg --fingerprint vsiveton
+
+</code></pre></div></section></section><section>
+<h2>Version: GnuPG v1.4.5 (MingW32)</h2></section><section>
+<h2>mQGiBEUrnAsRBACQDiYGc1IQmkENLO9iznBg8otGPEbzqQozT5tsip5mB30f6Mc/ uuLxJkLdna7Ul3goIXDtCeLJq38gHvruNtVNR6S+juJFkd5sLEH8UJ18PbKuo/9I KGlzjtCYUUDC48czRr0efhqd54NH8ydNdpaZ76NGPPYfpXtk7kKgH/nPiwCgxozK IG2frMuWIvdFafbqdAl7y/sD/1Csf0r9jtHEeXOuyhm8jCGrSwzLbHUGKPUQP37P ajECHoWp6HnvHEEEpgVl+UjfZvrcVhzUoP+3r5HAugqERfkzK8AWc7qjIRjf64kU sjvto31G2KYz17Y8K9y4LkRkUspu8uw903pKnW/QELg4vvPVaEYpVVIdS6+cUreu V0hOA/4tW7T/GpzSbQmjvnIRQ7GVHbQeXsANwrS6NmGYIxafN9P9dfHV+eUieTu6 rvMP9coOhTYyEKZksrXw2MmXx5SzgxsXT0g4wDXbwxPYFfIdGUzFMobnVXiZ3G8l JEl9cML0cg3ZL1SoDmVf2iG3e3Yxxsne4AE1SU+0bbq0t7rqALQlVmluY2VudCBT aXZldG9uIDx2c2l2ZXRvbkBhcGFjaGUub3JnPohgBBMRAgAgBQJFK5wLAhsDBgsJ CAcDAgQVAggDBBYCAwECHgECF4AACgkQhPTUcAfdtwLP3gCbB/V1afp8hzxgirCS d2r6zCkJQ2IAoLKD/RIkkerNintYzrubJliJKBsRuQINBEUrnBgQCAD1+Sx+sBDL 1XCDtxQGsrZmMnJJVK/w4TPa/8weJkuZ1GSpINOjInmqESuehvCLoOoyfcuDVXlR PUZhKZLPEKfJlFptGNK19oTO/CoQN+SJLwR41FoumsBaf1YSSRpAukyx2J6cUxqf uWrK/T8PmgDw4YzmY96tev//41eZ5tSOxpoUM8ypnTaShtS9pjgHijEG0b7wBqeU e1OGOiLHgKyjEJUmlT
aLm1SxJ84eq0uAvYb+rb/QoWWLpjvr2/mo1kzUvCPgo3fh kgOxCxsC9QD836Mi5HFK6CRYU3yAFu5+/jM+LJzELy3u7uMuOSP6yuiK8WXopdbN WHOiJQfdc2gTAAMFCADdljjAG7L+8de6JzsEduKErKqWlTEWa99n1knaGKzdUUOP WrKxwqgI6PAJbxOfG4vBdDa6M6+nySJDMybQsOCFyNx91/7jYkgkmv8Jkt8CTW4z P4HKlFYMAFpU95ftpTAAMAlr+t+nZRTHi94/VHMv4yLGzB/xapbzToHKuUt1Yqom Ncio5px7RVoicn13/i/GeY72fIdC2LRGo6PXlmmDQemoAnUw0RJoEtzapb0j/tWd BdAtQQX/Ks7qhk4aDDHGgO+CdHAB8PLHDpMpUX5Zc9JX1xhyJcS8d/LPUpXtt9WN eekqDpx+jNmySJr6os7rPAkjx6jDUvHPiuKdT4aviEkEGBECAAkFAkUrnBgCGwwA CgkQhPTUcAfdtwJL9ACgmLuDxE+oZaMhyFSmXWN0fM36Bd8AoLYrvwydB9+nNnhJ 85TjkMPTgjp9 =Hg4C —–END PGP PUBLIC KEY BLOCK—– —————-</h2>
+<p>You need to append this result to <a href="https://svn.apache.org/repos/asf/maven/project/KEYS" class="externalLink">https://svn.apache.org/repos/asf/maven/project/KEYS</a>.</p>
+<p>You also need to upload your key to the public server: <a href="http://pgp.mit.edu/" class="externalLink">http://pgp.mit.edu/</a> by copying the same you appended in the text field and submit. You can ensure by searching your email in key search engine.</p><section>
+<h3>gpg –fingerprint</h3>
+
+<div class="source"><pre class="prettyprint linenums"><code>>gpg --fingerprint vsiveton
pub 1024D/07DDB702 2006-10-10
Key fingerprint = 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
uid Vincent Siveton <vsiveton@apache.org>
-sub 2048g/D2814A59 2006-10-10</pre></div>
-<p>Go to <a class="externalLink" href="https://id.apache.org">https://id.apache.org</a>, log in and fill <code>OpenPGP Public Key Primary Fingerprint:</code> with the value of <code>Key fingerprint</code>.</p>
-<p>You can read more about <a class="externalLink" href="https://www.apache.org/dev/release-signing.html#faq">Checksums And Signatures</a>.</p></section></section>
+sub 2048g/D2814A59 2006-10-10
+</code></pre></div>
+<p>Go to <a href="https://id.apache.org" class="externalLink">https://id.apache.org</a>, log in and fill <code>OpenPGP Public Key Primary Fingerprint:</code> with the value of <code>Key fingerprint</code>.</p>
+<p>You can read more about <a href="https://www.apache.org/dev/release-signing.html#faq" class="externalLink">Checksums And Signatures</a>.</p></section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/retirement-plan-plugins.html
==============================================================================
--- maven/website/content/developers/retirement-plan-plugins.html (original)
+++ maven/website/content/developers/retirement-plan-plugins.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/retirement-plan-plugins.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/retirement-plan-plugins.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,8 +48,8 @@
<ul class="breadcrumb">
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
- <li class="active ">Retirement Plan for Plugins <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/retirement-plan-plugins.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li class="active ">Retirement Plan for Plugins <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/retirement-plan-plugins.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../download.cgi" title="Download">Download</a></li>
@@ -140,18 +140,35 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<section>
-<h1>Retirement Plan for Plugins</h1><section>
-<h2>Decide to retire</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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<section><section>
+<h2>Retirement Plan for Plugins</h2><section>
+<h3>Decide to retire</h3>
<p>Propose a vote on the dev-list to retire a plugin. The vote should be open for the standard 72 hours to allow people to voice their opinions. Send a cc to the users-list. Standard Apache voting rules apply. Only PMC votes are binding.</p>
<p>The vote must contain one or more options on how to retire the plugin. There are multiple scenarios available. Here are a couple that have been suggested:</p>
-<ol style="list-style-type: upper-alpha">
-<li>Move to our retired area in svn</li>
-<li>Move to another Apache project</li>
-<li>Move to www.mojohaus.org, apache-extras.org or another forge</li></ol>
+<p>A Move to our retired area in svn</p>
+<p>A Move to another Apache project</p>
+<p>A Move to <a href="http://www.mojohaus.org" class="externalLink">www.mojohaus.org</a>, apache-extras.org or another forge</p>
<p>Here's a template for scenario A that can be used for the vote email:</p>
-<div>
-<pre>To: "Maven Developers List" <dev@maven.apache.org>
+
+<div class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
Cc: "Maven Users List" <users@maven.apache.org>
Subject: [VOTE] Retire Maven Foo Plugin
@@ -172,10 +189,11 @@ https://maven.apache.org/developers/reti
The vote is open for 72 hours.
[ ] +1 Yes, it's about time
-[ ] -1 No, because...</pre></div>
+[ ] -1 No, because...
+</code></pre></div>
<p>If the vote is successful, post the result to the dev list and cc the PMC and users list. For instance:</p>
-<div>
-<pre>To: "Maven Developers List" <dev@maven.apache.org>
+
+<div class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
Cc: "Maven Users List" <users@maven.apache.org>
CC: "Maven Project Management Committee List" <private@maven.apache.org>
Subject: [RESULT] [VOTE] Retire Maven Foo Plugin
@@ -187,35 +205,37 @@ The vote has passed with the following r
+1 (binding): <<list of names>>
+1 (non binding): <<list of names>>
-I will continue with the steps required to retire this plugin.</pre></div>
+I will continue with the steps required to retire this plugin.
+</code></pre></div>
<p>If the vote passes, make one final release of the plugin (with its own standard 72h vote on source release) before it is retired. This allows us to make a clean break. The person who wants to retire a plugin is the one who does the final release. Below you will find the extra steps that you need to follow when retiring a plugin, in addition to <a href="./release/maven-project-release-procedure.html">our standard release process</a>.</p></section><section>
-<h2>Make the final release</h2>
-<ol style="list-style-type: decimal">
-<li>Create an issue in JIRA with the issue type "Task" and the summary "Retire this plugin", and schedule it for the final release. If the plugin includes a JIRA report in the generated site, you will need to close this issue before you make the release.</li>
-<li>Add the description "This is the final version of this plugin. It has been retired." to the final version in JIRA.</li>
-<li>Add a prominent notice on the front page of the plugin's site, informing that the plugin is retired. Suggested text:
-<div>
-<pre>Note: This plugin is retired. It is no longer maintained.</pre></div>
+<h3>Make the final release</h3>
+<p>1 Create an issue in JIRA with the issue type “Task” and the summary “Retire this plugin”, and schedule it for the final release. If the plugin includes a JIRA report in the generated site, you will need to close this issue before you make the release.</p>
+<p>1 Add the description “This is the final version of this plugin. It has been retired.” to the final version in JIRA.</p>
+<p>1 Add a prominent notice on the front page of the plugin's site, informing that the plugin is retired. Suggested text:</p>
+
+<div class="source"><pre class="prettyprint linenums"><code>Note: This plugin is retired. It is no longer maintained.
+</code></pre></div>
<p>If the plugin is moved elsewhere, that should also be added to the plugin's site. Suggested text:</p>
-<div>
-<pre>Note: This plugin has retired from the Apache Maven project,
-but has moved to the <Organization> <Project> project.</pre></div></li>
-<li>Add " (RETIRED)" at the end of <code><project></code>/<code><name></code> in the plugin's <code>pom.xml</code>. This will show up on every page of the generated site.</li>
-<li>Go ahead with <a href="./release/maven-project-release-procedure.html">the standard release process</a>, making sure that you follow the exceptions mentioned above regarding the site deployment.</li>
-<li>When updating the plugins page, move Maven Foo Plugin to under the "Retired" heading. Remove the SVN and JIRA links and add the date of retirement.</li>
-<li>When updating the version in JIRA, do not add Y.Z+1 and make sure you remove any future versions.</li></ol></section><section>
-<h2>Clean up after the release</h2>
-<ol style="list-style-type: decimal">
-<li>Remove the <code>.Jenkinsfile</code> from all branches. This will remove the project from https://builds.apache.org/job/maven-box/</li>
-<li>Ask INFRA for archive git repos (gitbox + github)</li>
-<li>Republish documentation, postfix project name with (RETIRED)</li>
-<li>When relevant update summary pages for <a class="externalLink" href="https://maven.apache.org/plugins/index.html">plugins</a> or <a class="externalLink" href="https://maven.apache.org/shared/index.html">shared components</a> </li>
-<li>Add " (RETIRED)" at the end of the project name in JIRA.</li>
-<li>Put the JIRA project in read-only mode in case of standalone project (own Jira key): apply Maven Retired Project Permissions Scheme. (Requires JIRA admin karma: e.g. ask Brian Fox)</li>
-<li>Comment the <a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool.conf.html">dist-tool configuration</a> entry.</li>
-<li>Remove distribution from current <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven/">dist area</a> (history remains available in <a class="externalLink" href="https://archive.apache.org/dist/maven/">archive</a>).</li>
-<li>Update board report</li>
-<li>Announce the fact that the plugin has been retired/moved on the announce@m.a.o and users@m.a.o mailing lists. Explain to people what they should do if they would like to continue development of the plugin.</li></ol></section></section>
+
+<div class="source"><pre class="prettyprint linenums"><code>Note: This plugin has retired from the Apache Maven project,
+but has moved to the <Organization> <Project> project.
+</code></pre></div>
+<p>1 Add " (RETIRED)" at the end of <code>\<project\></code>/<code>\<name\></code> in the plugin's <code>pom.xml</code>. This will show up on every page of the generated site.</p>
+<p>1 Go ahead with <a href="./release/maven-project-release-procedure.html">the standard release process</a>, making sure that you follow the exceptions mentioned above regarding the site deployment.</p>
+<p>1 When updating the plugins page, move Maven Foo Plugin to under the “Retired” heading. Remove the SVN and JIRA links and add the date of retirement.</p>
+<p>1 When updating the version in JIRA, do not add Y.Z+1 and make sure you remove any future versions.</p></section><section>
+<h3>Clean up after the release</h3>
+<p>1 Remove the <code>.Jenkinsfile</code> from all branches. This will remove the project from <a href="https://builds.apache.org/job/maven-box/" class="externalLink">https://builds.apache.org/job/maven-box/</a></p>
+<p>1 Ask INFRA for archive git repos (gitbox + github)</p>
+<p>1 Republish documentation, postfix project name with (RETIRED)</p>
+<p>1 When relevant update summary pages for <a href="https://maven.apache.org/plugins/index.html" class="externalLink">plugins</a> or <a href="https://maven.apache.org/shared/index.html" class="externalLink">shared components</a></p>
+<p>1 Add " (RETIRED)" at the end of the project name in JIRA.</p>
+<p>1 Put the JIRA project in read-only mode in case of standalone project (own Jira key): apply Maven Retired Project Permissions Scheme. (Requires JIRA admin karma: e.g. ask Brian Fox)</p>
+<p>1 Comment the <a href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool.conf.html" class="externalLink">dist-tool configuration</a> entry.</p>
+<p>1 Remove distribution from current <a href="https://dist.apache.org/repos/dist/release/maven/" class="externalLink">dist area</a> (history remains available in <a href="https://archive.apache.org/dist/maven/" class="externalLink">archive</a>).</p>
+<p>1 Update board report</p>
+<p>1 Announce the fact that the plugin has been retired/moved on the <a href="mailto:announce@m.a.o" class="externalLink">announce@m.a.o</a> and <a href="mailto:users@m.a.o" class="externalLink">users@m.a.o</a> mailing lists. Explain to people what they should do if they would like to continue development of the plugin.</p><!-- Insert template for retirement email here -->
+</section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/website/component-reference-documentation-helper.html
==============================================================================
--- maven/website/content/developers/website/component-reference-documentation-helper.html (original)
+++ maven/website/content/developers/website/component-reference-documentation-helper.html Thu Feb 9 00:34:05 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/website/component-reference-documentation-helper.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/website/component-reference-documentation-helper.md at 2023-02-09
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -47,7 +47,7 @@
<li class=""><a href="https://www.apache.org/" class="externalLink" title="Apache">Apache</a><span class="divider">/</span></li>
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class="active ">Preparing Component Release Documentation <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/website/component-reference-documentation-helper.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-08</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-02-09</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
<li class="pull-right"><a href="../../download.cgi" title="Download">Download</a></li>