console logs disappear after update to Spring Boot 2

[codefromthecrypt]

The following goes away if you manually exclude log4j:log4j from the kafka dep. However doing that breaks kafka, which has a hard dep on log4j1.2. Probably needs looking carefully at the spring logging bootstrap to see if it is a known issue when multiple logging libraries are present.

cc @shakuzen @zeagord

log4j:WARN No appenders could be found for logger (org.springframework.web.context.support.StandardServletEnvironment).
log4j:WARN Please initialize the log4j system properly.
                                    ********
                                  **        **
                                 *            *
                                **            **
                                **            **
                                 **          **
                                  **        **
                                    ********
                                      ****
                                      ****
        ****                          ****
     ******                           ****                                 ***
  ****************************************************************************
    *******                           ****                                 ***
        ****                          ****
                                       **
                                       **


             *****      **     *****     ** **       **     **   **
               **       **     **  *     ***         **     **** **
              **        **     *****     ****        **     **  ***
             ******     **     **        **  **      **     **   **

:: Powered by Spring Boot ::         (v2.0.1.RELEASE)

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.springframework.cglib.core.ReflectUtils$1 (jar:file:/Users/acole/oss/zipkin/zipkin-server/target/zipkin-server-2.8.2-SNAPSHOT-exec.jar!/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar!/) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of org.springframework.cglib.core.ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2018-04-29 19:13:07.033  INFO [/] 95304 --- [           main] org.xnio                                 : XNIO version 3.3.8.Final
2018-04-29 19:13:07.046  INFO [/] 95304 --- [           main] org.xnio.nio                             : XNIO NIO Implementation Version 3.3.8.Final
2018-04-29 19:13:07.119  WARN [/] 95304 --- [           main] io.undertow.websockets.jsr               : UT026009: XNIO worker was not set on WebSocketDeploymentInfo, the default worker will be used
2018-04-29 19:13:07.119  WARN [/] 95304 --- [           main] io.undertow.websockets.jsr               : UT026010: Buffer pool was not set on WebSocketDeploymentInfo, the default pool will be used
2018-04-29 19:13:07.140  INFO [/] 95304 --- [           main] io.undertow.servlet                      : Initializing Spring embedded WebApplicationContext
2018-04-29 19:13:08.214  INFO [/] 95304 --- [           main] com.datastax.driver.core                 : DataStax Java driver 3.5.0 for Apache Cassandra
2018-04-29 19:13:08.220  INFO [/] 95304 --- [           main] c.d.driver.core.GuavaCompatibility       : Detected Guava >= 19 in the classpath, using modern compatibility layer
2018-04-29 19:13:08.391  INFO [/] 95304 --- [           main] com.datastax.driver.core.ClockFactory    : Using native clock to generate timestamps.

[codefromthecrypt]

ps tried with java 1.8 same problem

[zeagord]

AFAIK Spring logging doesn't support multiple libs.
spring-projects/spring-boot#11148
spring-projects/spring-boot#10847

[codefromthecrypt]

ok so we need a solution that doesn't break Kafka. right now the exec jar tests (maven invoker) fail if we exclude the log4j jar. the point of the tests are to prove things work. so either our tests are wrong (false negative) or things are really broke if we do this and so need a different solution. note the Kafka version that breaks is 0.8 so KAFKA_ZOOKEEPER env is needed to manually test this.