To be honest, I don't fully understand the class loading issues, but I do know that JCL still has not resolved the problems despite knowing about them.
This worries me as well. There are lots of projects that have class loader related issues and can't seem to shake them. The whole reason for SLF4J's popularity is that it sheds class loader resolution of which logging framework to use and instead uses static linking.
No matter how many times you reiterate that there will be no problems or workload here, I don't buy it.
I don't see any compelling need or demand to make this change. And I don't believe that there won't be any problems. Once code is committed and used by the project, it becomes the burden of the whole community to support and maintain it. And frankly, I don't want to support a custom logging abstraction framework. I'd rather use a tried and true one that is very unlikely to cause any support or maintenance burden.
Jeremy
