Upgrading to 2.0.0.RELEASE from 1.5.10.RELEASE breaks logging behavior

Originally, my app is working with 1.5.10.RELEASE alongside Groovy, and I make my logging using Groovy’s @Log4j annotation and everything works fine; the logging is made using the configurations set in the application.properties, file is correctly updated and no undesired messages are shown. This is the configuration I’m originally using:

# Logging 
logging.file=application.log
logging.pattern.console=%clr(%d{yyyy-MM-dd HH:mm:ss.SSS}){faint} %clr(%5p) %clr(${PID:- }){magenta} %clr(---){faint} %clr([%15.15t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} [%X{correlationId}] %m%n%wEx
logging.pattern.file=%d{yyyy-MM-dd HH:mm:ss.SSS} %5p ${PID:- } --- [%t] %-40.40logger{39} : [%X{correlationId}] %m%n%wEx

When I try to upgrade to the 2.0.0.RELEASE, the logging is broken, in the sense that neither the messages I want to log are shown, nor the log file is updated correctly. Besides, my console gets saturated with log messages from external libraries I’m using, as if it was in some sort of Debug mode.

Any idea what’s going on? Might groovy annotations have conflicts with spring boot auto-configuration?

[jcarbad]

While making the sample project, the behavior was exactly as you mentioned, by getting a compilation error when using the @log4j. The erratic behavior was due to and old library using log4j. By changing the annotation to @Slf4j everything worked again.

Thanks a lot your help!

[PascalSchumacher]

@log4j is indeed backed by log4j1.x and requires log4j1.x on the classpath to work, see https://github.com/apache/groovy/blob/master/src/main/groovy/groovy/util/logging/Log4j.java