Remove Commons Logging in favor of Log4j 1.3 UGLI

Quote:

---

Originally Posted by jbetancourt

I vote for removing JCL use in Spring. Perhaps Spring should eat its own dog food and have the logging implementation injected into it. :)

---

JCL is an abstraction layer, not an implementation. The sole purpose of JCL is to decouple your app from any specific logging implementation. So by using JCL, Spring is already eating its own dog food. Or would you have Spring reinvent the wheel by providing its own logging abstraction layer?

Andrew

Excellent point. However, in this case reinventing the wheel may make sense.
Spring could have used other stuff too, like commons BeanUtils, but it does its own.

Though, if the latest commons logging fixed the reported problems, there is no need.