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/18 20:40:59 UTC
svn commit: r1907743 [3/21] - in /maven/website/content: ./ archives/maven-2.x/ developers/ developers/conventions/ developers/release/ developers/website/ docs/ docs/3.2.1/ docs/3.2.2/ docs/3.2.3/ docs/3.2.5/ docs/3.3.1/ docs/3.3.3/ docs/3.3.9/ docs/3...
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 Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/release/pmc-gpg-keys.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/release/pmc-gpg-keys.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,7 +48,7 @@
<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/markdown/developers/release/pmc-gpg-keys.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
@@ -139,30 +139,12 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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
+<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
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
@@ -235,32 +217,29 @@ 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
-
-</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"
+</pre></div></section><section>
+<h2>gpg --list-sigs && gpg --armor --export</h2>
+<div>
+<pre>>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>
-
-</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
+</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
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
-</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>
+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>
</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 Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/retirement-plan-plugins.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/retirement-plan-plugins.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,7 +48,7 @@
<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/markdown/developers/retirement-plan-plugins.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../scm.html" title="Get Sources">Get Sources</a></li>
@@ -140,35 +140,18 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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>
+<section>
+<h1>Retirement Plan for Plugins</h1><section>
+<h2>Decide to retire</h2>
<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>
-<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>
+<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>Here's a template for scenario A that can be used for the vote email:</p>
-
-<div class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
+<div>
+<pre>To: "Maven Developers List" <dev@maven.apache.org>
Cc: "Maven Users List" <users@maven.apache.org>
Subject: [VOTE] Retire Maven Foo Plugin
@@ -189,11 +172,10 @@ https://maven.apache.org/developers/reti
The vote is open for 72 hours.
[ ] +1 Yes, it's about time
-[ ] -1 No, because...
-</code></pre></div>
+[ ] -1 No, because...</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 class="source"><pre class="prettyprint linenums"><code>To: "Maven Developers List" <dev@maven.apache.org>
+<div>
+<pre>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
@@ -205,37 +187,35 @@ 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.
-</code></pre></div>
+I will continue with the steps required to retire this plugin.</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>
-<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>
+<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>
<p>If the plugin is moved elsewhere, that should also be added to the plugin's site. Suggested text:</p>
-
-<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> <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>
+<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>
</main>
</div>
</div>
Modified: maven/website/content/developers/website/deploy-component-reference-documentation.html
==============================================================================
--- maven/website/content/developers/website/deploy-component-reference-documentation.html (original)
+++ maven/website/content/developers/website/deploy-component-reference-documentation.html Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/website/deploy-component-reference-documentation.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/website/deploy-component-reference-documentation.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,7 +10,8 @@
<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="Barrie Treloar, Hervé Boutemy" />
+ <meta name="author" content="Barrie Treloar
+Hervé Boutemy" />
<meta name="date" content="2015-03-30" />
<title>Maven – Deploy Maven Component Reference Documentation</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
@@ -48,7 +49,7 @@
<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 ">Deploy Maven Component Reference Documentation <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/website/deploy-component-reference-documentation.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li class="active ">Deploy Maven Component Reference Documentation <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/website/deploy-component-reference-documentation.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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
@@ -137,102 +138,70 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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>
+<section>
+<h1>Introduction</h1>
<p>This document gives step-by-step instructions for deploying Maven components reference documentation inside the Maven <a href="/">https://maven.apache.org/</a> website.</p>
<p>See <a href="./index.html">Maven website introduction</a> for instructions on the whole website publication (main site content + components).</p></section><section>
-<h2>Overview</h2>
-<p>Since December 2012, the overall website uses svnpubsub mechanism:</p>
-<p><img src="component-reference-documentation.png" alt="" />Components reference documentation mechanisms overview</p></section><section>
-<h2>How components reference documentation publication works</h2>
-<p>Components don't use CMS: components reference documentation are versioned and generated from full sources, with both handwritten content (like Maven main site) and content generated from sources (javadoc, unit-test results, integration test results…).</p><section>
-<h3>Staging component reference documentation</h3>
+<h1>Overview</h1>
+<p>Since December 2012, the overall website uses svnpubsub mechanism:</p><figure><img src="component-reference-documentation.png" alt="" /><figcaption>Components reference documentation mechanisms overview</figcaption></figure></section><section>
+<h1>How components reference documentation publication works</h1>
+<p>Components don't use CMS: components reference documentation are versioned and generated from full sources, with both handwritten content (like Maven main site) and content generated from sources (javadoc, unit-test results, integration test results...).</p><section>
+<h2>Staging component reference documentation</h2>
<p>Reference documentation of a component is staged in <code>https://maven.apache.org/xxx-archives/yyy-LATEST/</code>, where <code>yyy</code> is the component name and <code>xxx</code> can be:</p>
<ul>
-
-<li>
-<p>the component type, like <code>shared</code>, <code>plugins</code>, <code>skins</code>, … (see <a href="/shared-archives/">/shared-archives/</a>, <a href="/plugins-archives/">/plugins-archives/</a>, <a href="/pom-archives/">/pom-archives/</a>, <a href="/skins-archives/">/skins-archives/</a>)</p></li>
-<li>
-<p>the component name for standalone components, like <code>archetype</code>, <code>plugin-tools</code>, <code>surefire</code>, <code>wagon</code>, … (see <a href="/archetype-archives/">/archetype-archives/</a>, <a href="/archetypes-archives/">/archetypes-archives/</a>, <a href="/plugin-tools-archives/">/plugin-tools-archives/</a>, <a href="/scm-archives/">/scm-archives/</a>, <a href="/surefire-archives/">/surefire-archives/</a>, <a href="/wagon-archives/">/wagon-archives/</a>)</p></li>
-</ul>
+<li>the component type, like <code>shared</code>, <code>plugins</code>, <code>skins</code>, ... (see <a href="/shared-archives/">/shared-archives/</a>, <a href="/plugins-archives/">/plugins-archives/</a>, <a href="/pom-archives/">/pom-archives/</a>, <a href="/skins-archives/">/skins-archives/</a>)</li>
+<li>the component name for standalone components, like <code>archetype</code>, <code>plugin-tools</code>, <code>surefire</code>, <code>wagon</code>, ... (see <a href="/archetype-archives/">/archetype-archives/</a>, <a href="/archetypes-archives/">/archetypes-archives/</a>, <a href="/plugin-tools-archives/">/plugin-tools-archives/</a>, <a href="/scm-archives/">/scm-archives/</a>, <a href="/surefire-archives/">/surefire-archives/</a>, <a href="/wagon-archives/">/wagon-archives/</a>)</li></ul>
<p>To publish component reference documentation:</p>
-<p>1 prerequisite: eventually build the component if it has not been done previously, or some reports may miss build or integration information:</p>
-<p>Notice: In cases where you have prepared a release you can simple change into <code>target/checkout</code> directory and continue with 2.</p>
-
-<div class="source"><pre class="prettyprint linenums"><code>mvn -Prun-its install
-</code></pre></div>
-<p>1 build the reference documentation:</p>
-
-<div class="source"><pre class="prettyprint linenums"><code>mvn -Preporting site site:stage
-</code></pre></div>
-<p>Notice: <code>site:stage</code> is really necessary only for multi-modules components, but added unconditionally in these instructions to keep them as straightforward as possible.</p>
-<p>1 stage the reference documentation to website production svn area, using <a href="/plugins/maven-scm-publish-plugin">maven-scm-publish-plugin</a>: (TODO: explanations on configuration in pom to yyy-LATEST)</p>
-
-<div class="source"><pre class="prettyprint linenums"><code>mvn scm-publish:publish-scm
-</code></pre></div>
-<p>svnpubsub mechanism transfers svn production content to live production site</p>
-<p><strong>Notice</strong>: content is in fact published to <a href="/components/">/components/</a> directory, and symbolic links declared in <code>resources/\*\*/components.links</code> in main site source are used by Ant to create a reference from <code>/xxx</code> (= what we want to be user-visible) to <code>/components/xxx</code> (what what is checked out).</p></section><section>
-<h3>Publishing versioned component reference documentation</h3>
+<ol style="list-style-type: decimal">
+<li>prerequisite: eventually build the component if it has not been done previously, or some reports may miss build or integration information:
+<p>Notice: In cases where you have prepared a release you can simple change into <code>target/checkout</code> folder and continue with 2.</p>
+<div>
+<pre>mvn -Prun-its install</pre></div></li>
+<li>build the reference documentation:
+<div>
+<pre>mvn -Preporting site site:stage</pre></div>
+<p>Notice: <code>site:stage</code> is really necessary only for multi-modules components, but added unconditionally in these instructions to keep them as straightforward as possible.</p></li>
+<li>stage the reference documentation to website production svn area, using <a href="/plugins/maven-scm-publish-plugin">maven-scm-publish-plugin</a>: (TODO: explanations on configuration in pom to yyy-LATEST)
+<div>
+<pre>mvn scm-publish:publish-scm</pre></div>
+<p>svnpubsub mechanism transfers svn production content to live production site</p></li></ol>
+<p><b>Notice</b>: content is in fact published to <a href="/components/">/components/</a> directory, and symbolic links declared in <code>resources/**/components.links</code> in main site source are used by Ant to create a reference from <code>/xxx</code> (= what we want to be user-visible) to <code>/components/xxx</code> (what what is checked out).</p></section><section>
+<h2>Publishing versioned component reference documentation</h2>
<p>When doing a release, <code>yyy-LATEST</code> content staged in previous section needs:</p>
-<p>1 to be archived to versioned directory before a newer revision is published into -LATEST,</p>
-<p>1 to replace the actual component reference documentation.</p>
+<ol style="list-style-type: decimal">
+<li>to be archived to versioned directory before a newer revision is published into -LATEST,</li>
+<li>to replace the actual component reference documentation.</li></ol>
<p>This is done with operations on website production svn area: you can use <a href="./component-reference-documentation-helper.html">Component Reference Documentation Helper</a> to easily prepare svnmucc command line.</p>
<p>If you prefer to do everything by hand from command templates, you can do either with <code>svn</code> command:</p>
<ul>
-
-<li>Unix:</li>
-</ul>
-
-<div class="source"><pre class="prettyprint linenums"><code>SVNPUBSUB=https://svn.apache.org/repos/asf/maven/website/components
+<li>Unix:
+<div>
+<pre>SVNPUBSUB=https://svn.apache.org/repos/asf/maven/website/components
svn cp $SVNPUBSUB/xxx-archives/yyy-LATEST $SVNPUBSUB/xxx-archives/yyy-$version -m "Archive versioned site."
svn rm $SVNPUBSUB/xxx/yyy -m "Remove old site."
-svn cp $SVNPUBSUB/xxx-archives/yyy-$version $SVNPUBSUB/xxx/yyy -m "Publish new site."
-</code></pre></div>
-<ul>
-
-<li>Windows:</li>
-</ul>
-
-<div class="source"><pre class="prettyprint linenums"><code>set SVNPUBSUB=https://svn.apache.org/repos/asf/maven/website/components
+svn cp $SVNPUBSUB/xxx-archives/yyy-$version $SVNPUBSUB/xxx/yyy -m "Publish new site."</pre></div></li>
+<li>Windows:
+<div>
+<pre>set SVNPUBSUB=https://svn.apache.org/repos/asf/maven/website/components
svn cp %SVNPUBSUB%/xxx-archives/yyy-LATEST %SVNPUBSUB%/xxx-archives/yyy-$version -m "Archive versioned site."
svn rm %SVNPUBSUB%/xxx/yyy -m "Remove old site."
-svn cp %SVNPUBSUB%/xxx-archives/yyy-$version %SVNPUBSUB%/xxx/yyy -m "Publish new site."
-</code></pre></div>
-<p>or with <a href="http://svnbook.red-bean.com/en/1.8/svn.ref.svnmucc.re.html" class="externalLink"><code>svnmucc</code> command</a>:</p>
-
-<div class="source"><pre class="prettyprint linenums"><code>svnmucc -m "Publish yyy $version documentation" \
+svn cp %SVNPUBSUB%/xxx-archives/yyy-$version %SVNPUBSUB%/xxx/yyy -m "Publish new site."</pre></div></li></ul>
+<p>or with <a class="externalLink" href="http://svnbook.red-bean.com/en/1.8/svn.ref.svnmucc.re.html"><code>svnmucc</code> command</a>:</p>
+<div>
+<pre>svnmucc -m "Publish yyy $version documentation" \
-U https://svn.apache.org/repos/asf/maven/website/components \
cp HEAD xxx-archives/yyy-LATEST xxx-archives/yyy-$version \
rm xxx/yyy \
- cp HEAD xxx-archives/yyy-LATEST xxx/yyy
-</code></pre></div></section><section>
-<h3>Updating index page in the Maven site</h3>
+ cp HEAD xxx-archives/yyy-LATEST xxx/yyy</pre></div></section><section>
+<h2>Updating index page in the Maven site</h2>
<p>Some component types have an index page refering to each components of the same type. This is the case for plugins (see <a href="/plugins/">index</a>), shared (see <a href="/shared/">index</a>), poms (see <a href="/pom/">index</a>) and skins (see <a href="/skins/">index</a>).</p>
<p>Update the version number and release date for the component in the <code>content/apt/xxx/index.apt</code> page.</p>
<p>See <a href="../website/deploy-maven-website.html">Deploy Maven website</a> for more in-depth instructions on main site content editing.</p>
-<p><strong>Notice</strong>: if you forget about updating the index page, dist-tool has a <a href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/" class="externalLink">report run daily</a> that will gently send a failure notification on <a href="mailto:notifications@maven.a.o" class="externalLink">notifications@maven.a.o</a> when “Check Errors” report is not empty.</p></section></section></section>
+<p><b>Notice</b>: if you forget about updating the index page, dist-tool has a <a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/">report run daily</a> that will gently send a failure notification on notifications@maven.a.o when "Check Errors" report is not empty.</p></section></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/website/deploy-maven-website.html
==============================================================================
--- maven/website/content/developers/website/deploy-maven-website.html (original)
+++ maven/website/content/developers/website/deploy-maven-website.html Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/website/deploy-maven-website.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/website/deploy-maven-website.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,7 +10,8 @@
<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="Barrie Treloar, Hervé Boutemy" />
+ <meta name="author" content="Barrie Treloar
+Hervé Boutemy" />
<meta name="date" content="2015-03-30" />
<title>Maven – Deploy Maven Main Website</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
@@ -48,7 +49,7 @@
<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 ">Deploy Maven Main Website <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/website/deploy-maven-website.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li class="active ">Deploy Maven Main Website <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/website/deploy-maven-website.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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
@@ -123,75 +124,45 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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>
+<section>
+<h1>Introduction</h1>
<p>This document gives step-by-step instructions for deploying the main Maven <a href="/">https://maven.apache.org</a> website.</p>
-<p><strong>Obsolete</strong> this documentation is obsolete: with the migration of site source to Git, Apache CMS is not used any more. It is replaced by Git edit (eventually through GitHub with the “edit” link accessible from breadcrumb) followed by Jenkins job to build and commit to svnpubsub.</p>
+<p><b>Obsolete</b> this documentation is obsolete: with the migration of site source to Git, Apache CMS is not used any more. It is replaced by Git edit (eventually through GitHub with the "edit" link accessible from breadcrumb) followed by Jenkins job to build and commit to svnpubsub.</p>
<p>See <a href="./index.html">Maven website introduction</a> for instructions on the whole website publication.</p></section><section>
-<h2>Overview</h2>
-<p>Since December 2012, the overall website uses svnpubsub mechanism and the main website uses Apache CMS:</p>
-<p><img src="main-website.png" alt="" />Main website mechanisms overview</p></section><section>
-<h2>How main website publication works</h2>
-<p>Maven main website (<a href="https://maven.apache.org" class="externalLink">https://maven.apache.org</a>) is generated with <a href="/plugins/maven-site-plugin">maven-site-plugin</a> from a source tree stored in svn: <a href="https://svn.apache.org/repos/asf/maven/site/trunk" class="externalLink">https://svn.apache.org/repos/asf/maven/site/trunk</a>.</p><section>
-<h3>Edit source content</h3>
+<h1>Overview</h1>
+<p>Since December 2012, the overall website uses svnpubsub mechanism and the main website uses Apache CMS:</p><figure><img src="main-website.png" alt="" /><figcaption>Main website mechanisms overview</figcaption></figure></section><section>
+<h1>How main website publication works</h1>
+<p>Maven main website (<a class="externalLink" href="https://maven.apache.org">https://maven.apache.org</a>) is generated with <a href="/plugins/maven-site-plugin">maven-site-plugin</a> from a source tree stored in svn: <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/site/trunk">https://svn.apache.org/repos/asf/maven/site/trunk</a>.</p><section>
+<h2>Edit source content</h2>
<p>You can edit source content in 2 ways:</p>
-<p>1 use <a href="https://cms.apache.org/maven/" class="externalLink">the CMS UI</a> through your web browser:</p>
+<ol style="list-style-type: decimal">
+<li>use <a class="externalLink" href="https://cms.apache.org/maven/">the CMS UI</a> through your web browser:
<ul>
-
-<li>
-<p>Go to <a href="https://cms.apache.org/maven/" class="externalLink">https://cms.apache.org/maven/</a>.</p></li>
-<li>
-<p>Click link “Get Maven Working Copy”.</p></li>
-<li>
-<p>Navigate to the content you want to modify.</p></li>
-<li>
-<p>Once you have modified the content, commit with the button “Submit”.</p></li>
-</ul>
-<p>1 checkout the source content locally, modify it with your favorite text editor, eventually test the result (<code>mvn site</code>), then check-in source modifications.</p>
-<p>After source tree is modified in svn, <a href="http://ci.apache.org/builders/maven-site-staging" class="externalLink">a Buildbot job</a> is triggered:</p>
-<p>1 it builds the HTML site using <a href="/plugins/maven-site-plugin">maven-site-plugin</a>: <code>mvn site</code>,</p>
-<p>1 it publishes generated HTML content to <a href="https://svn.apache.org/repos/infra/websites/staging/maven/trunk/content/" class="externalLink">CMS staging svn area</a>,</p>
-<p>1 svnpubsub mecanism transfers svn CMS staging content to live CMS staging site: <a href="http://maven.staging.apache.org" class="externalLink">http://maven.staging.apache.org</a>,</p></section><section>
-<h3>Publish site content</h3>
-<p>If everything is good, <strong>publish modifications</strong> using <a href="https://cms.apache.org/maven/publish" class="externalLink">CMS publish</a> action.</p>
+<li>Go to <a class="externalLink" href="https://cms.apache.org/maven/">https://cms.apache.org/maven/</a>.</li>
+<li>Click link "Get Maven Working Copy".</li>
+<li>Navigate to the content you want to modify.</li>
+<li>Once you have modified the content, commit with the button "Submit".</li></ul></li>
+<li>checkout the source content locally, modify it with your favorite text editor, eventually test the result (<code>mvn site</code>), then check-in source modifications.</li></ol>
+<p>After source tree is modified in svn, <a class="externalLink" href="http://ci.apache.org/builders/maven-site-staging">a Buildbot job</a> is triggered: </p>
+<ol style="list-style-type: decimal">
+<li>it builds the HTML site using <a href="/plugins/maven-site-plugin">maven-site-plugin</a>: <code>mvn site</code>,</li>
+<li>it publishes generated HTML content to <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/staging/maven/trunk/content/">CMS staging svn area</a>,</li>
+<li>svnpubsub mecanism transfers svn CMS staging content to live CMS staging site: <a class="externalLink" href="http://maven.staging.apache.org">http://maven.staging.apache.org</a>,</li></ol></section><section>
+<h2>Publish site content</h2>
+<p>If everything is good, <b>publish modifications</b> using <a class="externalLink" href="https://cms.apache.org/maven/publish">CMS publish</a> action.</p>
<p>Under the hood:</p>
-<p>1 CMS copies CMS staging svn area content to <a href="https://svn.apache.org/repos/infra/websites/production/maven/content/" class="externalLink">website production svn area</a>,</p>
-<p>1 svnpubsub mecanism transfers svn production content to live production site: <a href="http://maven.apache.org" class="externalLink">http://maven.apache.org</a>.</p></section></section><section>
-<h2>How Doxia website publication works</h2>
+<ol style="list-style-type: decimal">
+<li>CMS copies CMS staging svn area content to <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/production/maven/content/">website production svn area</a>,</li>
+<li>svnpubsub mecanism transfers svn production content to live production site: <a class="externalLink" href="http://maven.apache.org">http://maven.apache.org</a>.</li></ol></section></section><section>
+<h1>How Doxia website publication works</h1>
<p>Doxia uses the exact same mecanisms:</p>
<ul>
-
-<li>
-<p>you can edit <a href="https://svn.apache.org/repos/asf/maven/doxia/site/trunk" class="externalLink">svn source tree</a> either locally or through <a href="https://cms.apache.org/maven-doxia/" class="externalLink">CMS UI</a>,</p></li>
-<li>
-<p><a href="http://ci.apache.org/builders/maven-doxia-site-staging" class="externalLink">a Buildbot job</a> builds the site and updates <a href="https://svn.apache.org/repos/infra/websites/staging/maven-doxia/trunk/content/" class="externalLink">website staging svn area</a>,</p></li>
-<li>
-<p>svnpubsub published to <a href="http://maven-doxia.staging.apache.org" class="externalLink">live staging site</a>,</p></li>
-<li>
-<p>if everything is good, <strong>publish modifications</strong> using <a href="https://cms.apache.org/maven-doxia/publish" class="externalLink">CMS publish</a> action,</p></li>
-<li>
-<p>CMS copies CMS staging svn area content to <a href="https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/" class="externalLink">website production svn area</a>,</p></li>
-<li>
-<p>svnpubsub mecanism transfers svn production content to live production site: <a href="http://maven.apache.org/doxia" class="externalLink">http://maven.apache.org/doxia</a>, with its <a href="/doxia/extpaths.txt"><code>extpaths.txt</code></a></p></li>
-</ul></section></section>
+<li>you can edit <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/doxia/site/trunk">svn source tree</a> either locally or through <a class="externalLink" href="https://cms.apache.org/maven-doxia/">CMS UI</a>,</li>
+<li><a class="externalLink" href="http://ci.apache.org/builders/maven-doxia-site-staging">a Buildbot job</a> builds the site and updates <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/staging/maven-doxia/trunk/content/">website staging svn area</a>,</li>
+<li>svnpubsub published to <a class="externalLink" href="http://maven-doxia.staging.apache.org">live staging site</a>,</li>
+<li>if everything is good, <b>publish modifications</b> using <a class="externalLink" href="https://cms.apache.org/maven-doxia/publish">CMS publish</a> action,</li>
+<li>CMS copies CMS staging svn area content to <a class="externalLink" href="https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/">website production svn area</a>,</li>
+<li>svnpubsub mecanism transfers svn production content to live production site: <a class="externalLink" href="http://maven.apache.org/doxia">http://maven.apache.org/doxia</a>, with its <a href="/doxia/extpaths.txt"><code>extpaths.txt</code></a></li></ul></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/website/index.html
==============================================================================
--- maven/website/content/developers/website/index.html (original)
+++ maven/website/content/developers/website/index.html Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/website/index.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/website/index.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,7 +10,8 @@
<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="Barrie Treloar, Hervé Boutemy" />
+ <meta name="author" content="Barrie Treloar
+Hervé Boutemy" />
<meta name="date" content="2013-09-23" />
<title>Maven – Deploy Maven Website</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
@@ -48,7 +49,7 @@
<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 ">Deploy Maven Website <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/website/index.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li class="active ">Deploy Maven Website <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/website/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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
@@ -137,57 +138,25 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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>The Maven <a href="https://maven.apache.org" class="externalLink">https://maven.apache.org</a> website is composed from:</p>
+<section>
+<h1>Introduction</h1>
+<p>The Maven <a class="externalLink" href="https://maven.apache.org">https://maven.apache.org</a> website is composed from:</p>
<ul>
-
-<li>
-<p>a main content,</p></li>
-<li>
-<p>multiple components reference documentation, published for each component release.</p></li>
-</ul>
-<p>And <a href="https://maven.apache.org/doxia/" class="externalLink">Doxia</a> website has the same dual structure.</p>
-<p>These contents are stored in svn, and svnpubsub/svnwcsub maintains a working copy on the webservers in <code>/www/maven.apache.org/content</code> (see <a href="https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnwcsub/files/svnwcsub.conf#L123" class="externalLink"><code>svnwcsub</code> configured in infra Puppet</a>):</p>
+<li>a main content,</li>
+<li>multiple components reference documentation, published for each component release.</li></ul>
+<p>And <a class="externalLink" href="https://maven.apache.org/doxia/">Doxia</a> website has the same dual structure.</p>
+<p>These contents are stored in svn, and svnpubsub/svnwcsub maintains a working copy on the webservers in <code>/www/maven.apache.org/content</code> (see <a class="externalLink" href="https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnwcsub/files/svnwcsub.conf#L123"><code>svnwcsub</code> configured in infra Puppet</a>):</p>
<ul>
-
-<li>
-<p><code>/</code> comes from <a href="https://svn.apache.org/viewvc/maven/website/content/" class="externalLink">https://svn.apache.org/repos/asf/maven/website/content/</a></p></li>
-<li>
-<p><a href="https://maven.apache.org/components" class="externalLink"><code>/components</code></a> comes from <a href="https://svn.apache.org/repos/asf/maven/website/components/" class="externalLink">https://svn.apache.org/repos/asf/maven/website/components/</a></p></li>
-<li>
-<p><code>/doxia</code> comes from <a href="https://svn.apache.org/viewvc/maven/doxia/website/content/" class="externalLink">https://svn.apache.org/repos/asf/maven/doxia/website/content/</a></p></li>
-<li>
-<p><a href="https://maven.apache.org/doxia/components" class="externalLink"><code>/doxia/components</code></a> comes from <a href="https://svn.apache.org/repos/asf/maven/doxia/website/components/" class="externalLink">https://svn.apache.org/repos/asf/maven/doxia/website/components/</a></p></li>
-</ul>
-<p>and the link between main content and components reference documentation (for example from <code>/plugins/maven-xxx-plugin</code> to internal <code>/components/plugins/maven-xxx-plugin</code>) is done with symbolic links. These links are configured in <code>components.links</code> files in <code>content/resources/</code> and subdirectories, for example <a href="https://github.com/apache/maven-site/blob/master/content/resources/plugins/components.links" class="externalLink">plugins/components.links</a>.</p></section><section>
-<h2>How website publication works</h2>
+<li><code>/</code> comes from <a class="externalLink" href="https://svn.apache.org/viewvc/maven/website/content/">https://svn.apache.org/repos/asf/maven/website/content/</a></li>
+<li><a class="externalLink" href="https://maven.apache.org/components"><code>/components</code></a> comes from <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/website/components/">https://svn.apache.org/repos/asf/maven/website/components/</a></li>
+<li><code>/doxia</code> comes from <a class="externalLink" href="https://svn.apache.org/viewvc/maven/doxia/website/content/">https://svn.apache.org/repos/asf/maven/doxia/website/content/</a></li>
+<li><a class="externalLink" href="https://maven.apache.org/doxia/components"><code>/doxia/components</code></a> comes from <a class="externalLink" href="https://svn.apache.org/repos/asf/maven/doxia/website/components/">https://svn.apache.org/repos/asf/maven/doxia/website/components/</a></li></ul>
+<p>and the link between main content and components reference documentation (for example from <code>/plugins/maven-xxx-plugin</code> to internal <code>/components/plugins/maven-xxx-plugin</code>) is done with symbolic links. These links are configured in <code>components.links</code> files in <code>content/resources/</code> and subdirectories, for example <a class="externalLink" href="https://github.com/apache/maven-site/blob/master/content/resources/plugins/components.links">plugins/components.links</a>.</p></section><section>
+<h1>How website publication works</h1>
<p>Instructions on how to publish website content are split in separate documents:</p>
<ul>
-
-<li>
-<p>on every main content source commit (<a href="https://github.com/apache/maven-site" class="externalLink">maven-site.git</a> and <a href="https://github.com/apache/maven-doxia-site" class="externalLink">maven-doxia-site.git</a>), main content rebuild and publish is triggered through Jenkins jobs ( <a href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/" class="externalLink">maven-site job</a> and <a href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-doxia-site/" class="externalLink">doxia-site job</a>), which basically run <code>mvn site-deploy</code> (it can be run locally if CI is off…),</p></li>
-<li>
-<p>on every Maven component release, release manager follows “<a href="./deploy-component-reference-documentation.html">deploying Maven components reference documentation</a>”, eventually using <a href="./component-reference-documentation-helper.html">Component Reference Documentation Helper</a> to easily prepare <code>svnmucc</code> command line.</p></li>
-</ul></section></section>
+<li>on every main content source commit (<a class="externalLink" href="https://github.com/apache/maven-site">maven-site.git</a> and <a class="externalLink" href="https://github.com/apache/maven-doxia-site">maven-doxia-site.git</a>), main content rebuild and publish is triggered through Jenkins jobs ( <a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/">maven-site job</a> and <a class="externalLink" href="https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-doxia-site/">doxia-site job</a>), which basically run <code>mvn site-deploy</code> (it can be run locally if CI is off...),</li>
+<li>on every Maven component release, release manager follows "<a href="./deploy-component-reference-documentation.html">deploying Maven components reference documentation</a>", eventually using <a href="./component-reference-documentation-helper.html">Component Reference Documentation Helper</a> to easily prepare <code>svnmucc</code> command line.</li></ul></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/website/website-overview.html
==============================================================================
--- maven/website/content/developers/website/website-overview.html (original)
+++ maven/website/content/developers/website/website-overview.html Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/website/website-overview.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/website/website-overview.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -10,7 +10,8 @@
<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="Barrie Treloar, Hervé Boutemy" />
+ <meta name="author" content="Barrie Treloar
+Hervé Boutemy" />
<meta name="date" content="2013-09-23" />
<title>Maven – Deploy Maven Website</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
@@ -48,7 +49,7 @@
<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 ">Deploy Maven Website <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/website/website-overview.md"><img src="../../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li class="active ">Deploy Maven Website <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/website/website-overview.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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../../scm.html" title="Get Sources">Get Sources</a></li>
@@ -123,36 +124,13 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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>
+<section>
+<h1>Introduction</h1>
<p>The Maven <a href="/">https://maven.apache.org</a> website is composed from:</p>
<ul>
-
-<li>
-<p>a main content</p></li>
-<li>
-<p>multiple components reference documentation</p></li>
-</ul>
-<p><img src="website-overview.png" alt="" />Website mechanisms overview</p>
-<p>See <a href="./index.html">Maven website introduction</a> for instructions on website publication.</p></section></section>
+<li>a main content</li>
+<li>multiple components reference documentation</li></ul><figure><img src="website-overview.png" alt="" /><figcaption>Website mechanisms overview</figcaption></figure>
+<p>See <a href="./index.html">Maven website introduction</a> for instructions on website publication.</p></section>
</main>
</div>
</div>
Modified: maven/website/content/developers/welcome-to-new-committers.html
==============================================================================
--- maven/website/content/developers/welcome-to-new-committers.html (original)
+++ maven/website/content/developers/welcome-to-new-committers.html Sat Feb 18 20:40:58 2023
@@ -2,7 +2,7 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/developers/welcome-to-new-committers.md at 2023-02-18
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/developers/welcome-to-new-committers.apt at 2023-02-18
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="">
@@ -48,7 +48,7 @@
<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 ">Guide for new Maven committers <a href="https://github.com/apache/maven-site/tree/master/content/markdown/developers/welcome-to-new-committers.md"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
+ <li class="active ">Guide for new Maven committers <a href="https://github.com/apache/maven-site/tree/master/content/apt/developers/welcome-to-new-committers.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-18</li>
<li class="pull-right"><span class="divider">|</span>
<a href="../scm.html" title="Get Sources">Get Sources</a></li>
@@ -140,55 +140,25 @@
</div>
</header>
<main id="bodyColumn" class="span10" >
-<!--
-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>Guide for new Maven committers</h2>
+<section>
+<h1>Guide for new Maven committers</h1>
<p>First of all congratulations, thank you, and welcome to the fold! If you are reading this you've recently been voted in as committer on an Apache Maven project and there are a few things that need to be sorted out before you can participate fully.</p>
-<p>The first thing to get out of the way is sending in your contributor's license agreement (CLA). You can't participate at Apache until we have received your signed CLA, so go to the <a href="http://www.apache.org/licenses/#clas" class="externalLink">Apache website</a>, print out the CLA, sign it, and send it in ASAP.</p>
+<p>The first thing to get out of the way is sending in your contributor's license agreement (CLA). You can't participate at Apache until we have received your signed CLA, so go to the <a class="externalLink" href="http://www.apache.org/licenses/#clas">Apache website</a>, print out the CLA, sign it, and send it in ASAP.</p>
<p>Once you've dealt with your CLA, there are a some documents that pertain to Apache as a whole you should read:</p>
<ul>
-
-<li>
-<p><a href="http://www.apache.org/foundation/how-it-works.html" class="externalLink">How the ASF works</a></p></li>
-<li>
-<p><a href="http://www.apache.org/dev/new-committers-guide.html" class="externalLink">Guide for new committers</a></p></li>
-<li>
-<p><a href="http://www.apache.org/dev/committers.html" class="externalLink">The committers FAQ</a></p></li>
-<li>
-<p><a href="http://www.apache.org/foundation/voting.html" class="externalLink">How voting works</a></p></li>
-</ul>
+<li><a class="externalLink" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></li>
+<li><a class="externalLink" href="http://www.apache.org/dev/new-committers-guide.html">Guide for new committers</a></li>
+<li><a class="externalLink" href="http://www.apache.org/dev/committers.html">The committers FAQ</a></li>
+<li><a class="externalLink" href="http://www.apache.org/foundation/voting.html">How voting works</a> </li></ul>
<p>Here are the documents that pertain to Maven specifically:</p>
<ul>
-
-<li>
-<p><a href="/guides/development/guide-maven-development.html">Guide to Maven development</a></p></li>
-<li>
-<p><a href="/developers/committer-environment.html">Setup your committer environment</a></p></li>
-</ul>
+<li><a href="/guides/development/guide-maven-development.html">Guide to Maven development</a></li>
+<li><a href="/developers/committer-environment.html">Setup your committer environment</a></li></ul>
<p>And here are the specifics on setting up your Git access:</p>
<ul>
-
-<li><a href="http://www.apache.org/dev/version-control.html" class="externalLink">Apache's Source Code Repository</a></li>
-</ul>
+<li><a class="externalLink" href="http://www.apache.org/dev/version-control.html">Apache's Source Code Repository</a></li></ul>
<p>If you have any questions just ask! We're here to help, and looking forward to working with you!</p>
-<p>The Maven Team!</p></section></section>
+<p>The Maven Team!</p></section>
</main>
</div>
</div>
Modified: maven/website/content/docs/3.2.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.2.1/release-notes.html (original)
+++ maven/website/content/docs/3.2.1/release-notes.html Sat Feb 18 20:40:58 2023
@@ -139,6 +139,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h2>Maven 3.2.1</h2>
Modified: maven/website/content/docs/3.2.2/release-notes.html
==============================================================================
--- maven/website/content/docs/3.2.2/release-notes.html (original)
+++ maven/website/content/docs/3.2.2/release-notes.html Sat Feb 18 20:40:58 2023
@@ -139,6 +139,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h2>Maven 3.2.2</h2>
@@ -161,7 +164,7 @@ See the <a href="../../plugins/index.htm
<h3>Support version ranges in parent elements (<a href="https://issues.apache.org/jira/browse/MNG-2199" class="externalLink">MNG-2199</a>)</h3>
<p>Parent elements can now use bounded ranges in the version specification. You can now consistently use ranges for all intra-project dependencies, of which parents are a special case but still considered a dependency of projects that inherit from them. The following is now permissible:</p>
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project>
+<div class="source"><pre class="prettyprint linenums"><code><project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -183,7 +186,7 @@ See the <a href="../../plugins/index.htm
<h3>Update maven-plugin-plugin:descriptor default binding from generate-resources phase to process-classes (<a href="https://issues.apache.org/jira/browse/MNG-5346" class="externalLink">MNG-5346</a>)</h3>
<p>Now when you use create plugins that strictly use annotation processing to generate the descriptor, you can avoid the confusing configuration previously required. This is what you typically needed to include in order to run the descriptor generator on compiled classes and avoid errors.</p>
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml"> <pluginManagement>
+<div class="source"><pre class="prettyprint linenums"><code> <pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
Modified: maven/website/content/docs/3.2.3/release-notes.html
==============================================================================
--- maven/website/content/docs/3.2.3/release-notes.html (original)
+++ maven/website/content/docs/3.2.3/release-notes.html Sat Feb 18 20:40:58 2023
@@ -139,6 +139,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h2>Maven 3.2.3</h2>
Modified: maven/website/content/docs/3.2.5/release-notes.html
==============================================================================
--- maven/website/content/docs/3.2.5/release-notes.html (original)
+++ maven/website/content/docs/3.2.5/release-notes.html Sat Feb 18 20:40:58 2023
@@ -139,6 +139,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h2>Maven 3.2.5</h2>
Modified: maven/website/content/docs/3.3.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.3.1/release-notes.html (original)
+++ maven/website/content/docs/3.3.1/release-notes.html Sat Feb 18 20:40:58 2023
@@ -139,6 +139,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h2>Overview</h2>
@@ -176,7 +179,7 @@ well-known.</p></li>
<li>
<p>The handling of the <a href="https://issues.apache.org/jira/browse/MNG-3891" class="externalLink"><code>toolchains.xml</code></a> file has been adjusted with the
handling of <code>settings.xml</code> which means it will be searched within the
-<code>${maven.home}/conf/</code> directory and furthermore within the <code>${user.home}/.m2/</code> directory.</p></li>
+<code>${maven.home}/conf/</code> folder and furthermore within the <code>${user.home}/.m2/</code> folder.</p></li>
<li>
<p>For a better understanding and as an example of the <code>toolchains.xml</code> file has been added
to the <a href="https://issues.apache.org/jira/browse/MNG-5745" class="externalLink">Maven distribution</a>.</p></li>
@@ -195,7 +198,7 @@ in the spirit of global settings file<a
it simpler to use.</p></li>
<li>
<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.
+which contains the extension and put it manually into the <code>${MAVEN_HOME}/lib/ext</code> folder.
This means you had to change the Maven installation. The consequence was that everyone who likes
to use this needed to change it's installation and makes the on-boarding for a developer much
more inconvenient. The other option was to give the path to the jar on command line via
@@ -244,8 +247,8 @@ but this can now simple being done by de
<code>${maven.projectBasedir}/.mvn/maven.config</code> file which contains the
configuration options for the command line. 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. The <code>${maven.projectBasedir}/.mvn/maven.config</code>
-is located in the <code>${maven.projectBasedir}/.mvn/</code> directory which is in the root
-of a multi module build. This directory is part of the project and will be checked
+is located in the <code>${maven.projectBasedir}/.mvn/</code> folder which is in the root
+of a multi module build. This folder is part of the project and will be checked
in into your version control. This results in being picked by everybody who
checks out the project and no need to remember to call this project
via <code>mvn -T3 -U --fail-at-end clean package</code> instead of <code>mvn clean package</code>.</p></li>
@@ -281,7 +284,7 @@ between different configurations.</li>
</code></pre></div>
<p>The configuration which is used here can be defined in your pom by using an execution id <code>default-cli</code>.</p>
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project...>
+<div class="source"><pre class="prettyprint linenums"><code><project...>
<build>
<plugins>
@@ -305,7 +308,7 @@ between different configurations.</li>
<p>Starting with this Maven release you can now define several configuration for different
executions on command like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><project...>
+<div class="source"><pre class="prettyprint linenums"><code><project...>
<build>
<plugins>
Modified: maven/website/content/docs/3.3.3/release-notes.html
==============================================================================
--- maven/website/content/docs/3.3.3/release-notes.html (original)
+++ maven/website/content/docs/3.3.3/release-notes.html Sat Feb 18 20:40:58 2023
@@ -139,6 +139,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h2>Maven 3.3.3</h2>
Modified: maven/website/content/docs/3.3.9/release-notes.html
==============================================================================
--- maven/website/content/docs/3.3.9/release-notes.html (original)
+++ maven/website/content/docs/3.3.9/release-notes.html Sat Feb 18 20:40:58 2023
@@ -138,6 +138,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h1>Release Notes – Maven 3.3.9</h1>
@@ -241,7 +244,7 @@ with <a href="https://issues.apache.org/
<code>MAVEN_OPTS</code> and debugging options which has been fixed by <a href="https://issues.apache.org/jira/browse/MNG-5813" class="externalLink">MNG-5813</a>.</p></li>
<li>
<p>Since Maven 3.3.1 it is possible to have configurations stored on a per project base in the
-<code>${maven.projectBasedir}/.mvn</code> directory of the project. There you can use the <code>maven.config</code>
+<code>${maven.projectBasedir}/.mvn</code> folder of the project. There you can use the <code>maven.config</code>
file to store command line options instead of repeating them every time you call Maven.
In cases where this file has been empty Maven ended with a failure. This has been fixed
with <a href="https://issues.apache.org/jira/browse/MNG-5816" class="externalLink">MNG-5816</a>.</p></li>
@@ -265,7 +268,7 @@ is stripped away which could cause probl
has been fixed with <a href="https://issues.apache.org/jira/browse/MNG-5721" class="externalLink">MNG-5721</a>.</p></li>
<li>
<p>There had been several issues with the <code>mvn</code> script which are for example
-wrong locating the <code>.mvn</code> directory, nonportable shell constructs, wrongly setting
+wrong locating the <code>.mvn</code> folder, nonportable shell constructs, wrongly setting
‘maven.multiModuleProjectDirectory’ variable or directories which contain spaces. Those
issues have been fixed <a href="https://issues.apache.org/jira/browse/MNG-5786" class="externalLink">MNG-5786</a>, <a href="https://issues.apache.org/jira/browse/MNG-5858" class="externalLink">MNG-5858</a>,
<a href="https://issues.apache.org/jira/browse/MNG-5882" class="externalLink">MNG-5882</a> and <a href="https://issues.apache.org/jira/browse/MNG-5884" class="externalLink">MNG-5884</a>.</p></li>
Modified: maven/website/content/docs/3.5.0-alpha-1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.5.0-alpha-1/release-notes.html (original)
+++ maven/website/content/docs/3.5.0-alpha-1/release-notes.html Sat Feb 18 20:40:58 2023
@@ -138,6 +138,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h1>Release Notes – Maven 3.5.0-alpha-1</h1>
@@ -149,7 +152,7 @@
<p>This is an <i>ALPHA</i> release. There is the potential that features may be added/removed between this release and the first GA release in the 3.5.x release line.</p>
-<p><i>Please consult the Known Issues section below before use</i></p>
+<p><i>Please consult the Known Issues section below before use</i></p>
</div>
<p>Maven 3.5.0-alpha-1 is <a href="../../download.html">available for download</a>.</p>
Modified: maven/website/content/docs/3.5.0-beta-1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.5.0-beta-1/release-notes.html (original)
+++ maven/website/content/docs/3.5.0-beta-1/release-notes.html Sat Feb 18 20:40:58 2023
@@ -138,6 +138,9 @@
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/references/apt-format.html
-->
<section>
<h1>Release Notes – Maven 3.5.0-beta-1</h1>