Re: [release-plugin] No longer publish MD5 files to Apache's dev and release folders.

It seems that this does not carry sufficient specificity for uniquely identifying the artifact: https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L164-L166

Re: [release-plugin] No longer publish MD5 files to Apache's dev and release folders.

Note that I fixed the SHA-1 and SHA-256 files in SVN. Gary On Wed, Jun 13, 2018 at 9:45 AM Rob Tompkins wrote: > We don’t create the .md5 files that reside in nexus, it does when the > build get’s pushed up. So no concern there. Regarding the signatures, those > seem to be the ones from the -sr

Re: [release-plugin] No longer publish MD5 files to Apache's dev and release folders.

We don’t create the .md5 files that reside in nexus, it does when the build get’s pushed up. So no concern there. Regarding the signatures, those seem to be the ones from the -src artifacts. Reading more closely to see where that happened. Thinking about checking in text-1.4 to the unit tests an

[release-plugin] No longer publish MD5 files to Apache's dev and release folders.

Rob, While Nexus still uses MD5 files, we should no longer publish MD5 files to Apache's dev and release folders. I manually deleted the ones for Commons Text just now, which leaves us with SHA-1 and SHA-256. Gary