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 IntelliJ unit test runs we get this:

ERROR StatusLogger No Log4j 2 configuration file found. Using default 
configuration (logging only errors to the console), or user programmatically 
provided configurations. Set system property 'log4j2.debug' to show Log4j 2 
internal initialization logging. 
Seehttps://logging.apache.org/log4j/2.x/manual/configuration.html  for 
instructions on how to configure Log4j 2

That's really annoying and it looks like Geode is broken.  To fix this it was suggested that "we would have to add log4j-core to the classpath of unit tests to get log4j-api to stop complaining".

I think this should be done.  Any objections?


Reply via email to