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 <https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L164-L166> I’ll fix that now.
-Rob > On Jun 13, 2018, at 11:48 AM, Gary Gregory <[email protected]> wrote: > > 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 <[email protected]> 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 -src artifacts. Reading more closely to see >> where that happened. Thinking about checking in text-1.4 to the unit tests >> and using those artifacts as our unit testing mechanism. >> >> -Rob >> >>> On Jun 13, 2018, at 11:39 AM, Gary Gregory <[email protected]> >> wrote: >>> >>> 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 >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
