Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <42E6CBD6.3060706@atlassian.com>
Date: Wed, 27 Jul 2005 09:48:38 +1000
From: Nick Faiz <nick@atlassian.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [jira] Commented: (DIREVE-171) add log4j config patch
References: <1622723532.1119796737467.JavaMail.jira@ajax.apache.org>
	 <1034442050.1122367999998.JavaMail.jira@ajax.apache.org>
	 <8a8dec40050726035550b7471b@mail.gmail.com>
	 <6.0.3.0.0.20050726134551.03c09c00@torino>
 <8a8dec4005072615421d3e6bcc@mail.gmail.com>
In-Reply-To: <8a8dec4005072615421d3e6bcc@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


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/
--