[maven-site] branch master updated: update links

[hb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new a9541612 update links
a9541612 is described below

commit a954161237c0c43ea49bc531cb73e9ce07b70f4e
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sat Apr 16 10:15:07 2022 +0200

    update links
---
 .../release/maven-project-release-procedure.apt      | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/content/apt/developers/release/maven-project-release-procedure.apt b/content/apt/developers/release/maven-project-release-procedure.apt
index 4df9eb4d..776cf5e6 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -27,7 +27,7 @@
 Performing a Maven Project Release
 
   This document covers the common release procedures used by the Maven team to perform releases.
-  
+
 * {Prerequisites}
 
  Be sure that:
@@ -35,20 +35,20 @@ Performing a Maven Project Release
   * you have a recent Git client installed and on your shell's path.
 
   * 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: {{{https://maven.apache.org/docs/history.html}https://maven.apache.org/docs/history.html}}
+    can be found here: {{{/docs/history.html}https://maven.apache.org/docs/history.html}}
 
   * if you receive an OutOfMemoryError during the build, make sure to have set the environment variable <<<MAVEN_OPTS=-Xmx512m>>>
 
   * you must use Maven 3.3.9+.
-  
+
   * follow Apache environment configuration steps outlined at: {{{https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env}Publishing Maven Artifacts}}.
 
   []
 
 * Before you begin
-  
+
   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:
-  
+
   * {{{./maven-core-release.html} Releasing Maven Core}}
 
   * {{{./parent-pom-release.html} Releasing a parent POM}}
@@ -75,9 +75,9 @@ Performing a Maven Project Release
        {{{https://infra.apache.org/publishing-maven-artifacts.html}Publishing Maven Releases}}. 
 
  [[2]] Stage the latest documentation as explained in {{{../website/deploy-component-reference-documentation.html}deploying Maven components reference documentation}}.
- 
+
 * Call the vote
- 
+
  Propose a vote on the dev list with the closed issues, the issues left,
  the staging repository and the staging site. For instance:
 
@@ -169,10 +169,10 @@ I will promote the source release zip file to Apache distribution area and the a
 * Copy the source release to the Apache Distribution Area
 
   The official Apache release is the 'source-release' bundle distributed in <<<www.apache.org/dist>>>,
-  as described in {{{http://www.apache.org/dev/release-distribution}Apache release distribution policy}}.
+  as described in {{{https://www.apache.org/dev/release-distribution}Apache Release Distribution Policy}}.
   All releases for Maven must be copied to {{{https://www.apache.org/dist/maven/}the official Maven release area}}.
   
-  The release area is maintained with svnsubpub. To deliver a release, you add it to 
+  The release area is maintained with svnpubsub. To deliver a release, you add it to 
   {{{https://dist.apache.org/repos/dist/release/maven}the subversion repository for the dist area}}:
   add the release, its signature and sha512 checksum files, copying them from
   <<<target/checkout/target/>>> directory created during <<<mvn release:perform>>> step.
@@ -192,7 +192,7 @@ wagon/wagon-2.2-source-release.zip.asc
 wagon/wagon-2.2-source-release.zip.sha512
 --------
 
-  You should also run 'svn rm' as needed to clear out older releases.  As per {{{https://www.apache.org/dev/release.html#where-do-releases-go}the release policy}},
+  You should also run 'svn rm' as needed to clear out older releases.  As per {{{https://www.apache.org/legal/release-policy.html#where-do-releases-go}Apache Release Policy}},
   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.