Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 85817 invoked from network); 19 Oct 2005 16:19:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Oct 2005 16:19:35 -0000 Received: (qmail 78511 invoked by uid 500); 19 Oct 2005 16:19:34 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 78463 invoked by uid 500); 19 Oct 2005 16:19:34 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 78446 invoked by uid 99); 19 Oct 2005 16:19:34 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2005 09:19:34 -0700 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.74.184.209] (HELO mail.qos.ch) (212.74.184.209) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2005 09:19:33 -0700 Received: from kal.qos.ch (kal [192.168.1.3]) by mail.qos.ch (Postfix) with ESMTP id 5B3491070B7 for ; Wed, 19 Oct 2005 18:19:11 +0200 (CEST) Message-Id: <6.0.3.0.0.20051019180941.040702f8@torino> X-Sender: blocked@torino (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 19 Oct 2005 18:19:12 +0200 To: "Apache Directory Developers List" From: Ceki =?iso-8859-1?Q?G=FClc=FC?= Subject: Re: upgrading to nlog4j.1.2.17 In-Reply-To: <768dcb2e0510190905u6aa4ed2eu@mail.gmail.com> References: <32609e770510121234i14b9d05ds65816a8c2f9f9557@mail.gmail.com> <1129150991.18957.1.camel@wkslx01.iktek.com> <6.0.3.0.0.20051013170233.044a6d70@torino> <434E9500.20301@bellsouth.net> <6.0.3.0.0.20051019162523.04031d30@torino> <768dcb2e0510190738kac41499i@mail.gmail.com> <435663E6.30909@bellsouth.net> <768dcb2e0510190834r115b8a3s@mail.gmail.com> <4356693F.5060204@bellsouth.net> <768dcb2e0510190905u6aa4ed2eu@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N At 06:05 PM 10/19/2005, you wrote: >2005/10/20, Alex Karasulu= <aok123@bellsouth.net>: >>Hmmm I guess this is because of the Spring's dep on Log4J right? Then >>let's use Log4J with SLF4J across the board just to be consistent. WDYT? > >Spring uses Commons-Logging AFAIK. Later we will have to completely=20 >remove Spring dependency and provide ApacheDS-centric configuration=20 >schema. When we get rid of Spring, we can simply use nlog4j. Are you aware of jcl104-over-slf4j.jar ? http://slf4j.org/manual.html#gradual In other words, you can still use library X, e.g. Spring, which depends on JCL. However, if you replace commons-logging.jar with jcl104-over-slf4j.jar, then the selection of the underlying logging system will be done by SLF4J without the class loader headaches. The underlying logging system can be any of NOP, simple, jdk14 logging, log4j or NLOG4J. Spring's commons-logging dependency becomes a moot issue. I hope this is relevant to the discussion. Is it, by the way? >Trustin >-- >what we call human nature is actually human habit >-- >http://gleamynode.net/ --=20 Ceki G=FClc=FC The complete log4j manual: http://www.qos.ch/log4j/ Improve your Sudoku skills at http://www.sudoku-grok.com/