> On Jul 9, 2018, at 3:07 PM, Stefan Seelmann <[email protected]> wrote: > > * Future releases should not include md5 checksums, please see mail from > Henk with subject "checksum file Release Distribution Policy" and > https://www.apache.org/dev/release-distribution#sigs-and-sums. But > currently it's still allowed, right?
Hello, The rules for deploying to repository.apache.org still require md5 checksums on the artifacts. So, will continue uploading those, unless someone’s got a better idea. Here’s the errors after staging repo fails on close: failureMessage Missing MD5: '/org/apache/directory/fortress/fortress-core/2.0.1/fortress-core-2.0.1.jar.md5' failureMessage Missing MD5: '/org/apache/directory/fortress/fortress-core/2.0.1/fortress-core-2.0.1-sources.jar.md5' failureMessage Missing MD5: '/org/apache/directory/fortress/fortress-core/2.0.1/fortress-core-2.0.1.pom.md5' failureMessage Missing MD5: '/org/apache/directory/fortress/fortress-core/2.0.1/fortress-core-2.0.1-javadoc.jar.md5’ Thanks, —Shawn
