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-site.git
The following commit(s) were added to refs/heads/master by this push:
new 29bc21e add shell instructions to create sha512 files
29bc21e is described below
commit 29bc21e3dc9d2bb7ff61ce49cecf8a8600b9b5d1
Author: Hervé Boutemy <[email protected]>
AuthorDate: Wed Jun 2 21:38:56 2021 +0200
add shell instructions to create sha512 files
---
content/apt/developers/release/maven-project-release-procedure.apt | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/content/apt/developers/release/maven-project-release-procedure.apt
b/content/apt/developers/release/maven-project-release-procedure.apt
index d8d8242..7b2f8d0 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -178,7 +178,11 @@ I will promote the artifacts to the central repo.
<<<target/checkout/target/>>> directory created during <<<mvn
release:perform>>> step.
Currently this requires to be in maven-pmc group (see
{{{https://issues.apache.org/jira/browse/INFRA-5945}INFRA-5945}}).
If you are not a PMC member, drop a line to <[email protected]> and
ask them to do this step (and the next one) for you: the PMC member will
- get the source release bundle and its signature from Nexus staging
repository and will create sha512 checksum file by hand.
+ get the source release bundle and its signature from Nexus staging
repository and will create sha512 checksum file by hand, for example using
shell:
+
+--------
+for f in *.zip ; do echo -n $(sha512sum $f | cut -c -128) > $f.sha512 ; done
+--------
For example:
