> 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
As much as I agree that log4j should be standardized on, with the existence of at least the jdk 1.4 logging package, I think it is unrealistic to expect all the jakarta projects to standardize. People want choices. They don't want to be locked into any one package. They will accept being locked into commons-logging, but only because they can configure it after the fact to use a different backend package. And from the client point of view, lowest-common-denominator is usually just fine. Even from the log4j perspective, much of the power is in how the backend (appenders, loggers, etc) is configured; not in the creation of the logger and the reporting of the messages. What I don't understand is why commons-logging has to be so complicated. What is it with all that class loading stuff? I think we should document the various problems/issues that people are running into, especially in regards to log4j, and bring that list to the commons developers for resolution. If they are going to take on creating a package like commons-logging, then there is some responsibility that goes with it. Care to start the list on wiki? -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
