Use SLF4J, drom commons-logging

[GoogleCodeExporter]

Using commons-logging causes all kinds of classloader headache.
There's a very good description of the problems it causes and why at
http://www.qos.ch/logging/classloader.jsp.
I suggest switching to LSF4J (see http://www.slf4j.org/) to avoid these
problems.

Original issue reported on code.google.com by cn.cncon...@gmail.com on 6 Jun 2008 at 9:28

[GoogleCodeExporter]

I would like to suggest that neither is used. There is no need for a fancy 
logging
framework. 

Create a simple Logger interface with methods for debug/info/warn etc and have 
the
user define an implement and pass it thru the relevant classes. Naturally i 
would
include a null version that simply ignores messages and probably another that 
simply
prints messages. 

I appreciate slf sort of solves this problem but the last thing a small library 
needs
is more dependencies.

Original comment by miroslav...@gmail.com on 1 May 2010 at 10:21