I just tested this, and it works. But I encountered one issue, when testing from an SBT project, the transitive dependency for log4j-api did not work, I had to specify log4j-api explicitly. When testing from a Maven project, it worked as expected. Have anyone else tried this from SBT? Is this a bug in SBT, or have we done something wrong in the packaging?
On Sat, Apr 15, 2017 at 7:53 PM, Matt Sicker <boa...@gmail.com> wrote: > Hello all, this is the first release candidate for the first stand alone > release of the log4j-api-scala modules under their own repository. In order > to decouple the version from the log4j-core version release train, we've > decided to jump right ahead to 11. > > Staging repository: > https://repository.apache.org/content/repositories/orgapachelogging-1027/ > Git tag: 11.0-rc1 > Git URL: https://git-wip-us.apache.org/repos/asf/logging-log4j-scala.git > > To download all the artifacts, execute the following: > > wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate > https://repository.apache.org/content/repositories/ > orgapachelogging-1027/org/apache/logging/log4j/ > > There will be some migration pain regarding how to deploy the site, but > getting the sources, documentation, and binaries published is an important > step toward the general log4j repository modularization. > > This vote will be open for at least 72 hours. We need at least 3 +1s from > PMCs along with more +1s than -1s. > > -- > Matt Sicker <boa...@gmail.com> > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
