I'd be all for that, there is no interdependency but consistent logging
configuration is always nice. If you keep poking me I'll writeup a
little "how to switch" page since there are a few helpful tricks to make
sure commons-logging and log4j stay out of the project.
-Eric
On 08/13/2012 11:5
Should we start switching our portlets over as well?
On Aug 12, 2012, at 9:16 PM, Eric Dalquist wrote:
> I'd like to switch from commons-logging + log4j to slf4j + logback in 4.1.
> SLF4j has bridge APIs so no code needs to change just our pom and logging
> config. Logback is easier to config
I'd like to switch from commons-logging + log4j to slf4j + logback in
4.1. SLF4j has bridge APIs so no code needs to change just our pom and
logging config. Logback is easier to configure and includes a
java.util.logging bridge which is handy for a few libraries we use. I
have the work done in