[
https://issues.apache.org/jira/browse/JCR-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-4709:
---------------------------------
Description:
Providing a SHA argument to {{check-release.sh}} does not provide any benefit
as all checksums are provided as dedicated files(!) in the staging repository
[https://dist.apache.org/repos/dist/dev/jackabbit|https://dist.apache.org/repos/dist/dev/jackrabbit/]
and compared with the calculated values independent of any given SHA argument.
Also nowadays multiple checksums are used (SHA1, SHA512, MD5).
The provided argument is currently not compared with any other checksum value
(neither file nor calculated one).
was:
Providing a SHA argument to {{check-release.sh}} does not provide any benefit
as all checksums are provided as dedicated files(!) in the staging repository
[https://dist.apache.org/repos/dist/dev|https://dist.apache.org/repos/dist/dev.]
and compared with the calculated values independent of any given SHA argument.
Also nowadays multiple checksums are used (SHA1, SHA512, MD5).
> Check Release script: Get rid of SHA argument
> ---------------------------------------------
>
> Key: JCR-4709
> URL: https://issues.apache.org/jira/browse/JCR-4709
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> Providing a SHA argument to {{check-release.sh}} does not provide any benefit
> as all checksums are provided as dedicated files(!) in the staging repository
> [https://dist.apache.org/repos/dist/dev/jackabbit|https://dist.apache.org/repos/dist/dev/jackrabbit/]
> and compared with the calculated values independent of any given SHA
> argument.
> Also nowadays multiple checksums are used (SHA1, SHA512, MD5).
> The provided argument is currently not compared with any other checksum value
> (neither file nor calculated one).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
