Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of flamefew@gmail.com designates
 209.85.216.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E37BC6E.3090201@apache.org>
References: 
 <CAAqLGLO9WsPU=_exMsKZkC9pJvPq=S8AnQjjg4_8v4=N7dOojQ@mail.gmail.com>
	<CAPVuaYspFrdqa5diX2uNqd=3=eYiMfC5Tfr5470v6m_GeX6Mwg@mail.gmail.com>
	<4E37BC6E.3090201@apache.org>
Date: Tue, 2 Aug 2011 22:50:43 -0700
Message-ID: 
 <CAPVuaYs2p_MQtNUOzJ5gNb16bKHmpf2-F3RJy7Y3P6+mh5mPAQ@mail.gmail.com>
Subject: Re: [logging] logging vs slf4j
From: Henri Yandell <flamefew@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 2, 2011 at 1:59 AM, Emmanuel Bourg <ebourg@apache.org> wrote:
> Le 28/07/2011 22:01, Henri Yandell a =E9crit :
>>
>> Personally I'm happy for commons-logging to die. :)
>
> Yeah let's use java.util.logging instead :)

Primarily that I don't get the feeling we have a major community of
developers on c-logging. We implemented it because we needed something
for our other components (though many simply chose not to log), but it
was never the passion of anybody here (hopefully not an incorrect
statement). Robert, Simon and others put in tons of good work, but I
feel that was duty not passion.

So happy to see it die because it's something that's headed to
dormancy (be it stable or not).

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org