Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 44276 invoked from network); 21 Apr 2009 18:31:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Apr 2009 18:31:30 -0000 Received: (qmail 63764 invoked by uid 500); 21 Apr 2009 18:31:29 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 63637 invoked by uid 500); 21 Apr 2009 18:31:29 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 63627 invoked by uid 99); 21 Apr 2009 18:31:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2009 18:31:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com designates 209.85.146.183 as permitted sender) Received: from [209.85.146.183] (HELO wa-out-1112.google.com) (209.85.146.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2009 18:31:19 +0000 Received: by wa-out-1112.google.com with SMTP id j32so1668148waf.10 for ; Tue, 21 Apr 2009 11:30:58 -0700 (PDT) Received: by 10.114.37.1 with SMTP id k1mr4106817wak.172.1240338658345; Tue, 21 Apr 2009 11:30:58 -0700 (PDT) Received: from ?192.168.10.129? (adsl-66-51-196-164.dslextreme.com [66.51.196.164]) by mx.google.com with ESMTPS id g25sm9544062wag.43.2009.04.21.11.30.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 21 Apr 2009 11:30:56 -0700 (PDT) Message-Id: From: Ralph Goers To: "Commons Developers List" In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j? Date: Tue, 21 Apr 2009 11:30:54 -0700 References: <49ECDF6E.70502@doit.wisc.edu> <4A30EC8B-ABA6-4DC0-A766-6EB31A33B24A@dslextreme.com> <342A575A-ECF8-4892-A8B8-312B92DBCD8B@dslextreme.com> <25aac9fc0904210801g5cfcb13ao65df7df0a334fb17@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org On Apr 21, 2009, at 11:09 AM, Jochen Wiedmann wrote: > On Tue, Apr 21, 2009 at 5:01 PM, sebb wrote: > >> Well, the SLF4J website specifically says it is not necessary to >> recompile: >> >> http://www.slf4j.org/manual.html#swapping >> >> i.e. SLF4J chooses the logging implementation based in which logging >> implementation it finds on the classpath; there must be only one >> such. >> >> I'm not saying SLF4J is better or worse than CL, but they both allow >> the implementation to be configured without recompilation. > > Thanks, that means that I'll drawback from this discussion. I'd only > like to note that I'd clearly prefer, if we all could stick to a > single logging system, regardless what. > Thanks. But I'd really like to get back to what this topic was meant to be about. Commons currently uses Commons Logging. It is a very minimal API (too minimal if you ask me) and apparently still has some issues with how it binds to its implementation. The basic question is, what is next for Commons Logging? Is there any point in enhancing it to emulate SLF4J? Should it just stay more or less as it is while it slowly loses its customer base? I don't think there is much point in discussing what logging system Commons projects should use in the future without answering this. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org