Hi all,

We've made the move from Log4J at work to Logback with very positive
results.  They work very similarly, but Logback is just more
'polished'.

Any objections in getting rid of Log4J in favor of Logback as a
test/samples dependency?  Shiro does not have a logging implementation
dependency (just SLF4J's API), so this doesn't affect end users - just
how the developers use logging in test cases.  Logback also implements
the SLF4J API directly, so that means one less dependency in our pom -
no SLF4J binding implementation .jar necessary.

Thoughts?

Les

Reply via email to