[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426517#comment-16426517
]
Uwe Schindler commented on LUCENE-7935:
---------------------------------------
Thanks!
{quote}
bq. The ASF page on publishing Maven artifacts
(http://www.apache.org/dev/publishing-maven-artifacts.html) says we don't need
to provide MD5 or SHA1 files:
Nexus will create MD5 and SHA1 checksums on the fly
{quote}
I think there is also a problem on top: the maven-ant-plugin seems to generate
the checksums when executing an "uploading" (in our case to local folder, see
"artifact:deploy" in the build log). As this plugin is no longer maintained (or
is it?), we can't publish the new hashes anyways. I also think that Maven still
requires md5 files in its infrastructure (at least they require them at
sonatype when you close the repository).
> Release .sha512 hash files with our artifacts
> ---------------------------------------------
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-7935.patch, LUCENE-7935.patch,
> LUCENE-7935_smokefail.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
