Noticed this in the logback documents::
http://logback.qos.ch/manual/configuration.html#LevelChangePropagator
As of version 0.9.25, logback-classic ships with LevelChangePropagator,
an implementation of LoggerContextListener which
propagates changes made to the level of any logback-classic logger
onto the java.util.logging framework. Such propagation eliminates
the performance impact of disabled log statements. Instances of LogRecord
will be sent to logback (via SLF4J) only for enabled log
statements. This makes it reasonable for real-world applications to
use the jul-to-slf4j
bridge.
Gradle currently uses 0.9.24.
How many things directly utilized by gradle currently use JUL? If enough, it
might provide a measurable performance increase. I haven't dug through the
code to see if gradle is already wrapping the level changes to adjust JUL
logger levels, but doing it native in logback seems like a good idea.
-Spencer
