This is an automated email from the ASF dual-hosted git repository.
robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ws-axiom.git
The following commit(s) were added to refs/heads/master by this push:
new 8b8a7b917 Update devguide.xml with some more details learned since
last time
8b8a7b917 is described below
commit 8b8a7b917665e1c8f5a63e9a083705384f331c7e
Author: Robert Lazarski <[email protected]>
AuthorDate: Sun Dec 1 14:06:27 2024 -1000
Update devguide.xml with some more details learned since last time
---
devguide/src/docbkx/devguide.xml | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/devguide/src/docbkx/devguide.xml b/devguide/src/docbkx/devguide.xml
index 7f3c6f851..19b68e2b8 100644
--- a/devguide/src/docbkx/devguide.xml
+++ b/devguide/src/docbkx/devguide.xml
@@ -526,7 +526,7 @@
javax.xml.stream.XMLOutputFactory=com.bea.xml.stream.XMLOutputFactoryBase</progr
</step>
<step>
<para>
- Start the release process with the following command:
+ Start the release process with the following command -
use 'mvn release:rollback' to undo and be aware that in the main pom.xml there
is an apache parent that defines some plugin versions. See <link
xlink:href="https://maven.apache.org/pom/asf"/>
</para>
<screen>mvn release:prepare</screen>
<para>
@@ -563,9 +563,18 @@
javax.xml.stream.XMLOutputFactory=com.bea.xml.stream.XMLOutputFactoryBase</progr
</para>
<para>
If not yet done, export your public key and append it
to <link
xlink:href="https://dist.apache.org/repos/dist/release/ws/axiom/KEYS"/>.
+ </para>
+ <para>
+ If not yet done, export your public key to the dev
area and append it to <link
xlink:href="https://dist.apache.org/repos/dist/release/axis/axis2/java/rampart/KEYS"/>.
The command to export a public key is as follows:
</para>
<screen>gpg --armor --export
<replaceable>key_id</replaceable></screen>
+ <para>
+ If you have multiple keys, you can define a
~/.gnupg/gpg.conf file for a default. Note that while 'gpg --list-keys' will
show your public keys, using maven-release-plugin with the command
'release:perform' below requires 'gpg --list-secret-keys' to have a valid entry
that matches your public key, in order to create 'asc' files that are used to
verify the release artifcats. 'release:prepare' creates the sha512 checksum
files.
+ </para>
+ <para>
+ The created artifacts i.e. zip files can be checked
with, for example, sha512sum 'axiom-2.0.0-bin.zip' which should match the
generated sha512 files. In that example, use 'gpg --verify
axiom-2.0.0-bin.zip.asc axiom-2.0.0-bin.zip.asc to verify the artifacts were
signed correctly.
+ </para>
</step>
<step>
<para>
