You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2022/05/22 22:59:18 UTC
[maven-release] branch master updated: [MRELEASE-955] rename upgrade to migrate for consistency with m-site-p
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-release.git
The following commit(s) were added to refs/heads/master by this push:
new 5f9e7464 [MRELEASE-955] rename upgrade to migrate for consistency with m-site-p
5f9e7464 is described below
commit 5f9e7464de923be2d0ca163af0f4cc7341f88d06
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon May 23 00:59:15 2022 +0200
[MRELEASE-955] rename upgrade to migrate for consistency with m-site-p
---
.../src/site/apt/{upgrade.apt.vm => migrate.apt.vm} | 9 +++++----
maven-release-plugin/src/site/site.xml | 2 +-
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/maven-release-plugin/src/site/apt/upgrade.apt.vm b/maven-release-plugin/src/site/apt/migrate.apt.vm
similarity index 88%
rename from maven-release-plugin/src/site/apt/upgrade.apt.vm
rename to maven-release-plugin/src/site/apt/migrate.apt.vm
index 93f66930..27925cae 100644
--- a/maven-release-plugin/src/site/apt/upgrade.apt.vm
+++ b/maven-release-plugin/src/site/apt/migrate.apt.vm
@@ -1,5 +1,5 @@
------
- Upgrading Maven Release Plugin From 2 to 3
+ Migrate Maven Release Plugin From 2 to 3
------
------
2022-04-24
@@ -25,7 +25,7 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-Upgrading Maven Release Plugin From 2 to 3
+Migrate Maven Release Plugin From 2 to 3
* Context: Maven 3 and Maven 4
@@ -46,8 +46,9 @@ Upgrading Maven Release Plugin From 2 to 3
* for internal projects, just configure the <<<maven-source-plugin>>> for example
- * for projects published to Maven Central repository, you'll need to add also <<<maven-javadoc-plugin>>> and <<<maven-gpg-plugin>>>: see
- {{{https://central.sonatype.org/publish/publish-maven/}the documentation}}
+ * for projects {{{/repository/guide-central-repository-upload.html}published to Maven Central repository}}, you'll need to add also <<<maven-javadoc-plugin>>> and <<<maven-gpg-plugin>>>: see
+ {{{https://central.sonatype.org/publish/publish-maven/}the documentation}}. \
+ Notice: if you already published to Maven Central, there is a good chance the configuration has already been done in a parent POM.
[]
diff --git a/maven-release-plugin/src/site/site.xml b/maven-release-plugin/src/site/site.xml
index 0af8a8a5..12a8f0ea 100644
--- a/maven-release-plugin/src/site/site.xml
+++ b/maven-release-plugin/src/site/site.xml
@@ -44,7 +44,7 @@ under the License.
<item name="release:help" href="help-mojo.html"/>
</item>
<item name="Usage" href="usage.html"/>
- <item name="Upgrade" href="upgrade.html"/>
+ <item name="Migrate" href="migrate.html"/>
<item name="FAQ" href="faq.html"/>
<!-- According to https://issues.apache.org/jira/browse/MNGSITE-152 -->
<item name="License" href="http://www.apache.org/licenses/"/>