Hi Matt, You are missing asc and sha256 files from https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/
Gary On Sat, Jul 7, 2018 at 1:11 PM Matt Sicker <boa...@gmail.com> wrote: > Hi all, we have a brand new Log4j API to release, and this is the first > release candidate to work with. Below are links to various pieces of the > release for verification: > > GPG keys: > https://dist.apache.org/repos/dist/release/logging/KEYS > > Signed by Matt Sicker (748F15B2CF9BA8F024155E6ED7C92B70FA1C814D). > > Source and binary jars: > https://repository.apache.org/content/repositories/orgapachelogging-1036/ > > Website staging: > https://jvz.github.io/log4j-api-kotlin-staging/ > > Actual release artifacts (just the sources): > https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/ > > Kotlin info: > https://kotlinlang.org/ > > Some notes about this release: > > * There is no configuration in the pom to automate the creation of release > notes, rat checks, or source and binary zips/tarballs. Thus, the > convenience of providing binary artifacts is only extended to the Maven > repository version for now. > * There doesn't appear to be any generated API docs. > > -- > Matt Sicker <boa...@gmail.com> >
