Hi Erik,
the troubles comes when you integrate third-party stuff depending on
log4j (as I currently do). Having said this you have a strong point when
looking at http://www.qos.ch/logging/classloader.jsp
Cheers,
Siegfried Goeschl
Erik Hatcher wrote:
On Jul 12, 2007, at 9:03 AM, Siegfried Goeschl wrote:
would be using commons-logging an improvement? It is a common
requirement to hook up different logging infrastructure ..
My personal take on it is *adding* a dependency to keep functionality
the same isn't an improvement. JDK logging, while not with as many
bells and whistles as Commons Logging, log4j, etc, is plenty good enough
and keeps us away from many of logging JARmageddon headaches.
I'm not against a logging change should others have different opinions
with a strong case of improvement.
Erik
