Resolved: stick to Log4j for logging

A pretty clear reason why if it ain't broke, don't fix it.

http://radio.weblogs.com/0122027/2003/08/15.html

" The purpose of Commons Logging is not to isolate your code from
changes in the underlying logging framework. (That's certainly easy
enough to do on your own, and not really worth doing in the first
place given the ease of switching from one logging framework to
another.) The purpose of Commons Logging is not to somehow be more
useful than actual logging frameworks by being more general. The
purpose of Commons Logging is not to somehow take the logging world by
storm. In fact, there are very limited circumstances in which Commons
Logging is useful. If you're building a stand-alone application, don't
use commons-logging. If you're building an application server, don't
use commons-logging. If you're building a moderately large framework,
don't use commons-logging. If however, like the Jakarta Commons
project, you're building a tiny little component that you intend for
other developers to embed in their applications and frameworks, and
you believe that logging information might be useful to those clients,
and you can't be sure what logging framework they're going to want to
use, then commons-logging might be useful to you."