And you know what? We've been using Commons Logging for 4 years. Not once have we received a single issue reported or even a mailing list thread or forum post saying that the JCL Classloading is hurting someone.
What is this argument supposed to mean? JCL has some well-known class loader issues that are experienced by many projects. The fact that no one has reported this problem to us could mean either a) we don't have a wide enough user base yet for people to have the problem b) don't have a diverse enough user base to have an environment where someone has encountered the problems or c) they recognize it's a JCL problem and not a JSecurity problem and address it through the many posts/ forums out there regarding the JCL problem.
Either way, I don't think it's a compelling argument for introducing more magical class loader behavior in our application. If anything, it's an argument for replacing any existing class loader detection code with static binding or configuration.
Jeremy
