Re: [DISCUSS] log4j errors/warnings

Note: John's suggestions are some really good alternatives to consider instead of adding log4j-core to the unit testing classpaths. On Tue, Oct 22, 2019 at 11:31 AM John Blum wrote: > There are other ways of controlling the Log4j2 Status Logger other than > adding test dependencies. > > > For in

Re: [DISCUSS] log4j errors/warnings

Just to be clear... this does NOT cause any precheckin or CI failures. It's just noise caused by log4j-api nagging about the lack of a backend. On Tue, Oct 22, 2019 at 11:33 AM Xiaojian Zhou wrote: > In CI, I keep hitting "> Task :geode-assembly:defaultCacheConfig > > 09:13:37 < > https://concou

Re: [DISCUSS] log4j errors/warnings

In CI, I keep hitting "> Task :geode-assembly:defaultCacheConfig 09:13:37 ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core

Re: [DISCUSS] log4j errors/warnings

There are other ways of controlling the Log4j2 Status Logger other than adding test dependencies. For instance, you can: 1. Set the JVM System property org.apache.logging.log4j.simplelog.StatusLogger.level to "OFF". 2. Theoretically, when Lo4j2 finds a log4j2 or log4j2-test Properties, YAML, JS

Re: [DISCUSS] log4j errors/warnings

I hit this problem in PR. I am just curious why it did not happen before? On Tue, Oct 22, 2019 at 9:44 AM Kirk Lund wrote: > I'm ok with adding log4j-core to the testRuntime for all unit test targets > to prevent the ERROR message. Any other input? > > On Fri, Oct 18, 2019 at 3:10 PM John Blum

Re: [DISCUSS] log4j errors/warnings

I'm ok with adding log4j-core to the testRuntime for all unit test targets to prevent the ERROR message. Any other input? On Fri, Oct 18, 2019 at 3:10 PM John Blum wrote: > Be careful to only add logging dependencies as testRuntime dependencies. > Do not add any logger implementation/provider (e

Re: [DISCUSS] log4j errors/warnings

Be careful to only add logging dependencies as testRuntime dependencies. Do not add any logger implementation/provider (e.g. log4j-core, or otherwise) in either the compile-time or runtime scope. This also means that when users are using and running Apache Geode applications (regardless of context

[DISCUSS] log4j errors/warnings

Not long ago changes were made to the sub-projects that introduced a lot of build noise.  In gradle builds we see a lot of this: ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... and in Intelli