Well, it seems the build fixes to drop md5 and generate sha512 didn't work for this artifact (embarassed-emoji), and when I built the uimaj-core with -Papache-release, it only added the .asc signing (no SHA512).
Investigating... -Marshall On 10/1/2018 3:13 PM, Marshall Schor wrote: > parent-pom-12 rc2 is posted and ready for voting. > > This release generates SHA-512 checksums instead of SHA1 checksums and deletes > the MD5 ones, per the recent change in the ASF release policy. > > It also updates the Apache-wide parent pom to the current level (21) from 18. > Many plugins which used to have versions specified by the uima-wide pom now > inherit (more recent) versions from the Apache-wide parent pom. > > It also adds a common profile for running the backwards compatibility report > generation. > > Other minor update: merged the 3 Jiras into one named Jira release named > parent-pom-12, to be consistent with what was already present. > > Tested with uimaj and uv3-uimaj and the eclipse update site for uimaj. > > > The changes are documented in these Jiras: > > https://issues.apache.org/jira/projects/UIMA/versions/12342864 > > This is a pom - only release. > > The maven staging repo is here: > > https://repository.apache.org/content/repositories/orgapacheuima-1198/ > > The svn tag is here: > > https://svn.apache.org/repos/asf/uima/build/tags/parent-pom-12/ > > Please vote on release: > > [ ] +1 OK to release > [ ] 0 Don't care > [ ] -1 Not OK to release, because ... > > Thanks. > > -- Marshall > > >
