directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Faiz <n...@atlassian.com>
Subject Re: [jira] Commented: (DIREVE-171) add log4j config patch
Date Tue, 26 Jul 2005 23:48:38 GMT

Actually, to make things transparent I will create a logging plan page, 
on the wiki, outlining the ideas I have in mind and asking for feedback 
from others, including best usages (such as log.debug("hello {}", 
getName()) ), etc.. I'll post a list to the URL when it's there.

Hopefully, this will make things clearer. I'll use the project's wiki.

Cheers,
Nick


Nick Faiz wrote:
> Hi Ceki,
>  
> Thanks for paying attention to our use of slf4j. I agree with you.
> Please remember, though, that this is just a patch which provides one
> thing - a configuration for slf4j which works for development.
> 
> The patch attached to DIREVE171 is a simple step forward - it is not
> the entire logging picture. So far it's taken 5 weeks to apply this
> one, small thing. I want to get it through before raising further
> logging ideas, which could take more time.
> 
> Further work on logging will occur in subsequent patches, however, and
> I'll be discussing it with the list. If you would be interested in
> providing feedback then I would obviously welcome it.
> 
> Cheers,
> Nick 
> 
> 
> 
> 
> On 7/26/05, Ceki Gülcü <listid@qos.ch> wrote:
> 
>>Hi Nick,
>>
>>I might be completely off base in this particular case, but in
>>general, a library-type component should NOT configure log4j and let
>>the user do it. Of course, you can still document logging in your
>>library, in particular by providing one or more sample configuration
>>files. The point is that you should not *impose* a log4j config file
>>on the end-user.
>>
>>In the case of application (and not a library), you can provide a
>>default log4j configuration file, but you should be careful to allow
>>the end-user change it if she wants to.
>>
>>As basic rule of thumb, you should view logging mostly as an end-user
>>concern. I hope these general remarks are helpful to you rather than a
>>distraction,
>>
>>
>>At 12:55 PM 7/26/2005, Nick Faiz wrote:
>>
>>>Hi Ceki,
>>>
>>>Yes, that sounds like a good idea.
>>>
>>>Right now, imo, the main issue is to get the logging configuration in
>>>place - as a dependency in project.xml for apacheds, so people can use
>>>it. Afterwards, the pattern layout can change, the logging statements
>>>can be altered.
>>>
>>>The 'Better alternative based on format messages' in
>>>http://www.slf4j.org/faq.html#2.3 looks really good.
>>>
>>>Cheers,
>>>Nick
>>
>>--
>>Ceki Gülcü
>>
>>   The complete log4j manual: http://www.qos.ch/log4j/
>>
>>
>>
> 
> 


-- 
ATLASSIAN - http://www.atlassian.com/

Confluence - the enterprise wiki - tried it yet?
http://www.atlassian.com/confluence/
--

Mime
View raw message