[
https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208628#comment-17208628
]
Michael Osipov edited comment on SLING-7534 at 10/6/20, 10:03 AM:
------------------------------------------------------------------
Deploying checkusm to a repo is documented
[here|https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html].
Use Resolver 1.6.1 and add
{{{{}}{{-Daether.checksums.algorithms}}=SHA-512,SHA-256,SHA-1,MD5}}. Try that
with snapshots first.
was (Author: michael-o):
Deploying checkusm to a repo is documented
[here|https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html].
Use Resolver 1.6.1 and add
{{-D{{aether.checksums.algorithms}}=SHA-512,SHA-256,SHA-1,MD5}}. Try that with
snapshots first.
> Release policy - stop providing MD5 and start providing SHA-512 checksums
> -------------------------------------------------------------------------
>
> Key: SLING-7534
> URL: https://issues.apache.org/jira/browse/SLING-7534
> Project: Sling
> Issue Type: Task
> Components: Tooling
> Reporter: Robert Munteanu
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Parent 40
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> See http://www.apache.org/dev/release-distribution#sigs-and-sums , we SHOULD
> no longer provide MD5 checksums for new releases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
