[
https://issues.apache.org/jira/browse/MPOM-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470380#comment-17470380
]
Herve Boutemy edited comment on MPOM-282 at 1/7/22, 7:12 AM:
-------------------------------------------------------------
INFRA-22540 is another pass at that same root cause issue, this time seen as
ASF's Nexus Repository staging rules level (repository.apache.org) to check
file existence, but not on file format (which is implicitely meant as "format
for Maven2 repository format on checksums")
was (Author: hboutemy):
INFRA-22540 is another pass at that same root cause issue, this time seen as
ASF's Nexus Repository staging rules level (repository.apache.org)
> Create correct SHA512 content
> -----------------------------
>
> Key: MPOM-282
> URL: https://issues.apache.org/jira/browse/MPOM-282
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
> Reporter: Karl Heinz Marbaise
> Priority: Minor
>
> Currently the created SHA512 which is used for the distribution area contains
> only the checksum but not the filename which results in bad output if the
> checksums being checked via command line tool:
> {code}
> $ shasum -c apache-maven-3.2.5-bin.tar.gz.sha512
> $ shasum: apache-maven-3.2.5-bin.tar.gz.sha512: no properly formatted SHA
> checksum lines found
> {code}
> The checksum should be enhanced to support that correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
