You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2022/11/27 22:36:04 UTC
[maven-site] branch changes-plugin updated (78979d56 -> 6b5354e3)
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch changes-plugin
in repository https://gitbox.apache.org/repos/asf/maven-site.git
omit 78979d56 Remove outdated references to Maven Changes Plugin
add e4e0bf2e Bump maven-parent from 38-SNAPSHOT to 39-SNAPSHOT
new 6b5354e3 Remove outdated references to Maven Changes Plugin
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (78979d56)
\
N -- N -- N refs/heads/changes-plugin (6b5354e3)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[maven-site] 01/01: Remove outdated references to Maven Changes Plugin
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch changes-plugin
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 6b5354e34573005452f8161249a618494dd6f466
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Sun Nov 27 23:15:17 2022 +0100
Remove outdated references to Maven Changes Plugin
---
.../release/maven-project-release-procedure.apt | 28 +---------------------
1 file changed, 1 insertion(+), 27 deletions(-)
diff --git a/content/apt/developers/release/maven-project-release-procedure.apt b/content/apt/developers/release/maven-project-release-procedure.apt
index a22b50f6..5268d6d5 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -278,30 +278,6 @@ wagon/wagon-2.2-source-release.zip.sha512
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.
- [[a]] Using Maven Changes Plugin
-
- If you are releasing a plugin or a shared component you can let Maven Changes Plugin <<generate>>, and eventually even
- <<send>>, the announcement for you. First make sure that you have configured the necessary
- properties in your {{{../committer-settings.html}committer settings}}.
-
-------
-cd target/checkout
-mvn changes:announcement-mail -Papache-release
-------
-
- If sending the mail should fail, the generated announcement is available in <<<target/announcement>>> (see <<<announcement.vm>>>)
- and you can use it as a base for sending the mail manually.
-
- If your SMTP server requires authentication you need to add the command line
- options for it:
-
-------
-cd target/checkout
-mvn changes:announcement-mail -Dchanges.username=<SMTP-USERNAME> -Dchanges.password=<SMTP-PASSWORD> -Papache-release
-------
-
- [[b]] Manually
-
<<Note:>> You must send this email from your apache email account, e.g. YOUR_APACHE_USERNAME@apache.org otherwise
the email to <<<...@maven.apache.org>>> will bounce.
@@ -339,9 +315,7 @@ Enjoy,
-----
- []
-
- [[6]] If releasing the Apache Parent POM, notify <<<...@apache.org>>>:
+ [[6]] If releasing the Apache Parent POM, notify <<<...@apache.org>>>:
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.