The issue here is between those who
a) want to use commons-logging (with default behaviour) out-of-box,
b) want to use commons-logging in a Log4J enabled application, out-of-box.
Both have reasonable requests & desires... the problem may be Log4J's
difficult bootstrapping mechanism.
It's been proposed (but nothing has yet been done) that the current content
be packaged in a number of different ways:
Create a commons-logging-XYZ.jar for each of LogKit, JDK14, SimpleLogger, ?
Log, LogFactory, appropriate LogImpl
We could include TWO versions for Log4J if we change the current logic
to NOT automatically defer to the Log4jFactory:
a) Log, LogFactory, appropriate LogImpl
b) Log, LogFactory, appropriate LogImpl, Log4jFactory
the first would work in an environment pre-enabled for Log4J.
The second would work in a clean environment.
So... the solution would be to grab the jar file that fits your environment.