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:28:02 UTC

[maven-site] branch changes-plugin created (now 78979d56)

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


      at 78979d56 Remove outdated references to Maven Changes Plugin

This branch includes the following new commits:

     new 78979d56 Remove outdated references to Maven Changes Plugin

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.



[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 78979d563c38330a440e479663a6fcd4713a6a84
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.