And don't include any kind of log4j configuration file inside the jar.
(had some app server logs VERY cluttered because someone from another area of the company sent me a packaged library with an included log4j.xml file with the root logger at debug level... :) On 7/28/06, James Stauffer <[EMAIL PROTECTED]> wrote:
Use automatic configuration so the the user of the library can change the configuration and don't include the log4j.jar or classes in your jar. On 7/28/06, Jitendra Kharche <[EMAIL PROTECTED]> wrote: > Hi, > > I am writing a library and want to know any practice followed to use > logger in a library. > Thanks in advance. > > Regards, > Jitendra > > -- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Javier González Nicolini --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
