Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 26820 invoked from network); 19 May 2009 12:41:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 May 2009 12:41:42 -0000 Received: (qmail 81604 invoked by uid 500); 19 May 2009 12:41:41 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 81488 invoked by uid 500); 19 May 2009 12:41:41 -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 81478 invoked by uid 99); 19 May 2009 12:41:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 12:41:41 +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: local policy) Received: from [85.218.33.218] (HELO mail.qos.ch) (85.218.33.218) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 12:41:31 +0000 Received: by mail.qos.ch (Postfix, from userid 1006) id C713F2293D7; Tue, 19 May 2009 14:43:42 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.5-gr0 (2008-06-10) on torino X-Spam-Level: Received: from [192.168.1.7] (unknown [192.168.1.7]) by mail.qos.ch (Postfix) with ESMTP id 0C4D2229397 for ; Tue, 19 May 2009 14:43:41 +0200 (CEST) Message-ID: <4A12A8E8.1020608@qos.ch> Date: Tue, 19 May 2009 14:41:12 +0200 From: Ceki Gulcu User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Commons Developers List Subject: Re: commons-logging version 0.0.0-EMPTY References: <1e379fc30905172157j7ebfd571xd632cfd9cf9f682e@mail.gmail.com> <4A116391.1030005@qos.ch> <4A11BA32.5080007@apache.org> <4A128792.9070104@qos.ch> <4A12A00E.8020301@qos.ch> <4c39e3030905190512w69ae8a3aj352cd1dee6823602@mail.gmail.com> In-Reply-To: <4c39e3030905190512w69ae8a3aj352cd1dee6823602@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-4.4 required=5.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5-gr0 nicolas de loof wrote: > A library autor that MAY use cl-0.0 to remove commons-logging from > dependency tree and use SLF4J will anyway have a dependency on cl-over-sfl4j > that solves the ClassNotFoundException Good point but what if the end-user wanted to use commons-logging proper and not SLF4J? In other words, can the end-user override the propagation of cl-0.0-EMPTY and use cl-1.1 instead? Clearly, by declaring cl-1.1 in the project POM, the end-user can reinstate cl-1.1. > A library that uses slf4j would anyway only declare slf4japi as dependency > and has no reason to force exclusion of commons-logging. I agree. Nevertheless, there is a possibility that 0.0-EMPTY would be propagated to the end-user, either accidentally or by incompetence. -- Ceki G�lc� Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org