> -----Original Message----- > From: Ceki G�lc� [mailto:[EMAIL PROTECTED]] > I never suspected (nor suggested) that commons-logging effort > was dishonorable in any way. My contention is that it will > make life harder not easier. Nothing more, nothing less. >
I think it may make life harder for the commons, Log4J, and LogKit teams, but I have already seen it make life easier for users of jakarta products. Digester used to have its own configuration mechanism, and it used to System.out.println() all *logging* information. Try using that in a server framework and see how fast you get angry when everything else uses Log4J. OK, so if Digester uses Log4J, now see how fast all the LogKit zealots will refuse to use it. Commons-logging was a way to plug into logging frameworks without dictating any of them. The main point IMHO was to remove System.out.println() calls. It happened to end up usefully wrapping all logging impls IMHO. That is a win for everyone. If we have problems with interoperability (and we will), we fix them. Yes, someone has to ultimately dictate the logger to use. As a commons developer, I do not want to force that choice onto anyone. Let them decide. Scott Sanders -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
