[commons-release-plugin] branch master updated: Define RM properties in settings.xml

[se...@apache.org]

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

sebb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new eaeb653  Define RM properties in settings.xml
eaeb653 is described below

commit eaeb653d9b2b9f1e86a88fcf690e71dbccad14d1
Author: Sebb <se...@apache.org>
AuthorDate: Sat Aug 1 14:54:20 2020 +0100

    Define RM properties in settings.xml
---
 src/site/xdoc/index.xml | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index f458442..e354cdd 100755
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -118,6 +118,32 @@
     </properties>
 ]]></source>
             <p>
+            Ensure your Release Manager details are defined in your Maven <code>~/.m2/settings.xml</code> file
+            (These are used by the vote-txt goal)
+            Properties have to be defined in a profile. For example:
+            </p>
+<source><![CDATA[
+<settings>
+  ...
+  <profiles>
+    ...
+    <profile>
+      <id>active-profile</id>
+      <properties>
+        <commons.releaseManagerName>Your Name</commons.releaseManagerName>
+        <commons.releaseManagerKey>Your Signing Key Hex ID</commons.releaseManagerKey>
+      </properties>
+    </profile>
+  </profiles>
+
+  <activeProfiles>
+    <!-- define active profile name -->
+    <activeProfile>active-profile</activeProfile>
+  </activeProfiles>
+  ...
+</settings>
+]]></source>
+            <p>
             After the above configuration performing the release would occur by (<i>note.</i> more
             in depth details can be found at
             <a href="https://commons.apache.org/releases/prepare.html">Preparations For A Release</a>):