[
https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208092#comment-17208092
]
Andrea Tarocchi edited comment on SLING-7534 at 10/5/20, 1:56 PM:
------------------------------------------------------------------
[~kwin] If I got all this correctly:
https://issues.apache.org/jira/browse/MRESOLVER-56 has been reverted so we need
to use `net.nicoulaj.maven.plugins:checksum-maven-plugin``` to generate
sha512/256 checksum, but then those checksum files are md5/sha1 checked again
during upload to nexus?
was (Author: valdar):
[~kwin] If I got all this correctly:
https://issues.apache.org/jira/browse/MRESOLVER-140 has been reverted so we
need to use `net.nicoulaj.maven.plugins:checksum-maven-plugin``` to generate
sha512/256 checksum, but then those checksum files are md5/sha1 checked again
during upload to nexus?
> 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)
