On Mon, Jul 14, 2008 at 5:18 PM, Jeremy Haile <[EMAIL PROTECTED]> wrote: >> 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.
Yep, you're right - all three of these are most likely. I was just saying that my solution is better than JCL because it still relies on SLF4J, but does a few extra convenient things, and that if it was in place, we could probably go just as long if not indefinitely before we heard any negative feedback. That's all. In other words, my proposed solution is still better than what we had in place until two days ago.
