Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.dillon@gmail.com
 designates 209.85.146.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender;
        b=D3Zw9tkuZCZPAVQENo9llyBzeQ5XFmMEzmHToDemq+SJ1F8+AXJeM2tM+3xLJBX1H7Nico7qfvo1NPT31IkogqeEeGByHcuOJ/pJHL43RjNKaX5b3gMtGbaJXej1+9KYvkWOUXEjhkANdLNJd78c1r/eFpKlwz/FxOPEubMR1Vo=
Message-Id: <D20E09B2-E030-4DE0-895F-616CA118DDFC@planet57.com>
From: Jason Dillon <jason@planet57.com>
To: dev@geronimo.apache.org
In-Reply-To: <3CE97398-A7B9-4B1F-9A2B-5D3EF9D009B8@yahoo.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: SLF4J over Commons Logging
Date: Thu, 24 Apr 2008 22:26:30 +0700
References: <511C8549-AF11-45F3-9C30-3CA648FC0B06@planet57.com>
 <3CE97398-A7B9-4B1F-9A2B-5D3EF9D009B8@yahoo.com>
Sender: Jason Dillon <jason.dillon@gmail.com>

Aight... well, ~9 hours later, I think its working or at 99%  I need  
to re-add support for the org.apache.geronimo.log.ConsoleLogLevel  
property, perhaps even add a special bootstrap SLF4J impl, but I think  
that the work is almost ready to commit.

Re-building to see how the testsuite fairs with my latest changes...  
and I have to go pick up my mom at the airport, but I hope to get this  
committed later tonight :-)

--jason


On Apr 24, 2008, at 5:18 AM, David Jencks wrote:

> +higher than I can count :-)
>
> thanks
> david jencks
>
> On Apr 23, 2008, at 1:25 PM, Jason Dillon wrote:
>
>> Yo yo... we've talked about this before, though a while ago... but  
>> IMO its about time we drop Commons Logging like a rock and move  
>> over to SLF4J.
>>
>> The API is mostly the same, though SLF4J has native support for  
>> things like:
>>
>>   log.trace()
>>
>> And has additional varargs support for things like:
>>
>>   log.info("this is my foo: {}", foo)
>>
>> I can dig up the old email I posted hella long ago if needed, but I  
>> think its time to switch over.  Its been on the shelf for too long  
>> already IMO.  I'm ready to start updating things to use the new  
>> API, but before I do I want to get a general consensus from the  
>> group.
>>
>> So chime in... failure to chime in means you agree with me :-P
>>
>> :-)
>>
>> --jason
>