Eelco Hillenius wrote:
But Al, maybe you want to share what problems this would fix for you?
TBH, I rely on so many other libraries that use commons-logging in most of my projects, that this isn't specifically going to fix anything for me. However, I've enough hours dealing with nasty commons-logging classloader pain to feel that the world would be a better place without it, and that we should help to hasten its demise.
Even once you have commons-logging set up properly, with all the JARs in the right place, it hangs onto things internally, preventing your webapp's classloader from being garbage collected, and leading to your container OutOfMemorying when you hot-deploy things. You need to call Introspector.flushCaches() and all the rest of it in an attempt to fix this, and the whole thing just isn't obvious or nice. SLF4J is.
So yeah, I guess this isn't terribly important, but I figure it'd be nice. Al
