[jbosscache-dev] Updated to commons-logging 1.1.1 (for now...)

[Navin Surtani]

For those who don't know me - I'm Manik's brother and interning with  
redhat ...

To continue the wondrous conversations that I have with Manik - what's  
the advantage of using slf4j over commons logging?




On 18 Aug 2008, at 18:52, Manik Surtani wrote:

> I'd rather go with JDK logging then.  IIRC, jboss-logging can  
> intercept JDK logging events and log to the preferred engine, and  
> this means fewer jars and NO DIRECT dependency on a lousy logging jar!

+ a lot on that one. I really think that it's easier not having any  
unwanted dependencies. Although nobody has talked about log4j for a  
while ... so why not throw that into the mix of the various kinds of  
loggings :D


>
>
>
> On 18 Aug 2008, at 18:47, Jason T. Greene wrote:
>
>> The last time this was discussed, the collective answer is that  
>> jboss logging is the preferred wrapper framework, since we control  
>> its destiny, but that the AS would add adapters for all popular  
>> frameworks. For example, hibernate's decision *cough* mistake  
>> *cough* lead to work on an sl4j adapter.
>>
>> JDK logging is also acceptable, since it's the standard one.
>>
>> Manik Surtani wrote:
>>> I think JGroups is the only one.  I think we need to sort out some  
>>> sort of logging standard for JBoss.  Who wants to bell THAT cat,  
>>> now?  :-)
>>> On 18 Aug 2008, at 14:57, Bela Ban wrote:
>>>> I agree on the insanity of it all. Good that JGroups is not the  
>>>> only dep which requires you to suck in commons-logging... :-)
>>>>
>>>> Manik Surtani wrote:
>>>>> It *is* commons logging.
>>>>>
>>>>> On 16 Aug 2008, at 09:12, Bela Ban wrote:
>>>>>
>>>>>> Actually, which logging library does JBossCache use today ? I  
>>>>>> thought it was commons-logging...
>>>>>>
>>>>>> Jason T. Greene wrote:
>>>>>>> Manik Surtani wrote:
>>>>>>>>
>>>>>>>
>>>>>
>>>>> <SNIP />
>>>>>
>>>>>>>> Hmm, another jar dep.  We need commons logging anyway for  
>>>>>>>> JGroups.
>>>>>>>
>>>>>>> Unfortunately I already have to include JBoss Logging since  
>>>>>>> AOP uses it.
>>>>>
>>>>> For chrissake. Why on earth is LOGGING of all things such a  
>>>>> challenge?  So this means using JBC with Hibernate will NOW need  
>>>>> commons logging (JBC, JGroups), jboss logging (AOP) and slf4j  
>>>>> (Hibernate), and all the while the JDK provides logging as  
>>>>> well?!?  This is insane.
>>>>>
>>>>> -- 
>>>>> Manik Surtani
>>>>> Lead, JBoss Cache
>>>>> manik at jboss.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> -- 
>>>> Bela Ban
>>>> Lead JGroups / Clustering Team
>>>> JBoss - a division of Red Hat
>>>>
>>> -- 
>>> Manik Surtani
>>> Lead, JBoss Cache
>>> manik at jboss.org
>>
>>
>> -- 
>> Jason T. Greene
>> JBoss, a division of Red Hat
>
> --
> Manik Surtani
> Lead, JBoss Cache
> manik at jboss.org
>
>
>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev