I’ll make sure to add links to the SHA-2 sums on the download page. The
MD5/SHA-1 sums are required by Maven Central IIRC. The asc signature should
be using SHA-2 at least I believe.

On Sat, Feb 1, 2020 at 19:59 Gary Gregory <[email protected]> wrote:

> On Sat, Feb 1, 2020 at 6:43 PM Ralph Goers <[email protected]>
> wrote:
>
> > I didn’t try to run it but based on a cursory examination of the web site
> > and artifacts - I did notice the site mentions md5 instead of sha256 and
> > sha512.
> >
>
> Note that the proper sha256/512 are here
> https://dist.apache.org/repos/dist/dev/logging/log4j/scala/
> Nexus does its own old fashioned thing with MD5s...
>
> Gary
>
>
> > +1
> >
> > Ralph
> >
> > > On Feb 1, 2020, at 3:38 PM, Matt Sicker <[email protected]> wrote:
> > >
> > > This is a vote to release Log4j Scala API 12.0-rc1. This vote will
> > > remain open for at least 72 hours and requires 3 +1 votes and more +1
> > > than -1 votes.
> > >
> > > Highlights:
> > > * Uses SBT instead of Maven!
> > > * Supports Scala 2.13!
> > > * New website!
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachelogging-1051
> > >
> > > Staging artifacts:
> > > https://dist.apache.org/repos/dist/dev/logging/log4j/scala/
> > >
> > > Site preview:
> > > https://jvz.github.io/log4j-scala-site/
> > >
> > > Repository:
> > > https://gitbox.apache.org/repos/asf?p=logging-log4j-scala.git
> > >
> > > Tag:
> > > v12.0
> > >
> > > You may download all the Maven artifacts by executing:
> > > wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> > >
> https://repository.apache.org/content/repositories/orgapachelogging-1051
> > >
> > > Notes about this release:
> > > * I notice that the site needs to be updated to include links to the
> > > sha256 and sha512 files in the downloads page.
> > > * The ScalaDoc links need to be updated with the proper location.
> > > * The ScalaDocs all need to be aggregated (again?) to ensure they're
> > > all on the site.
> > >
> > > --
> > > Matt Sicker <[email protected]>
> > >
> >
> >
> >
>
-- 
Matt Sicker <[email protected]>

Reply via email to