Howdy, >commons-logging developers, feel free to flame me and tell me how >wrong I am. Maybe you will open my eyes? Until then, my opinion is >that commons-logging should just stop existing and quit bugging-up >apps like Struts and others that get poisoned by commons-logging. I >cringe when I see an app I am interested in using it.
I actually share your opinion to a large degree, and cringe as well under the same circumstances. I think we (the Apache community) would gain from: - Establishing log4j as the standard logging component - Using log4j directly, i.e. bundling it with tomcat, struts, whatever - Eliminating commons-logging I didn't hear anyone complaining about logging among JBoss users when they (the JBoss group) bundled log4j and used it for their internal logging. I think they did a good thing. However, that said, the reality is that commons-logging is alive and used in applications. If it's possible at all, it'll take at the minimum significant time, effort, and a few releases in order to make it go away. So what do we do? I tend to think log4j should stick to what it does: provide excellent full-featured logging to those who want it. I also think from the commons-logging developer perspective, they can't anticipate all the possible classloading configurations and issues for people using commons-logging. Or can they? And for my third thought of this paragraph, I think if an app (especially a container like tomcat) chooses to use commons-logging, it is responsible for ensuring smooth co-operation between its clients and log4j and other logging toolkits. It's just venting, mostly on my part. But I think there's an alarming rise in the incidence of users running into problems around the various mailing lists. I don't want people to download tomcat (comes with commons-logging), try to use log4j, and be scared by configuration difficulty. It's a red flag for me if Ceki has problems in using his own system (log4j) under a certain configuration!!! That would make normal users run away back into System.err.println() land. Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
