RE: Next alpha or nightly build?

> -Original Message- > From: Curt Arnold [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 14, 2007 4:13 PM > To: Log4J Users List > Subject: Re: Next alpha or nightly build? > > > On Feb 14, 2007, at 12:22 PM, Gary Gregory wrote: > > > Hello: > > > > When can we get a new alpha build?

Re: Next alpha or nightly build?

On Feb 14, 2007, at 12:22 PM, Gary Gregory wrote: Hello: When can we get a new alpha build? There are fixes we'd like to pick up. Are there nightly builds somewhere? Thank you. Gary Gregory Senior Software Engineer Seagull Software [EMAIL PROTECTED] www.seagullsoft

Re: logger at method level

Try Logger.getLogger(Klass.class.getName() +".metod"); Besides that it should work just fine. On 2/14/07, Reshat Sabiq <[EMAIL PROTECTED]> wrote: Do i understand correctly that the following will work just fine log4j.logger.com.domain.paket.Klass.metod=DEBUG, CONSOLE, FILE2 as long as i constru

logger at method level

Do i understand correctly that the following will work just fine log4j.logger.com.domain.paket.Klass.metod=DEBUG, CONSOLE, FILE2 as long as i construct the Logger w/ Logger.getLogger(Klass.class+".metod"); I might not actually use this, cause it sounds too convoluted, but it's a thing i've been c

RE: 1.3alpha-8 question

Chainsaw V2 has been available for over 3 years, is stable and relatively bug free. Chainsaw V2's dependency on log4j 1.3 is that it stores logging event information internally using the log4j 1.3 LoggingEvent class. It also provides a way to define 'receivers', which first became available in

RE: 1.3alpha-8 question

Chainsaw V2 has been available for over 3 years and is stable and relatively bug free. Chainsaw V2's dependency on log4j 1.3 is that it stores logging event information internally using the log4j 1.3 LoggingEvent class. It also provides a way to define 'receivers', which first became available

Re: appender-ref to SMTPAppender knocks out log4j

Wyss Patrick wrote: if it's working otherwise then make sure that you have all needed libraries in your classpath (mail.jar, activation.jar) I had these two jars in the web application, but not at the level of the application server (Jetty), which is where the log4j jar lives. After adding th

re: appender-ref to SMTPAppender knocks out log4j

> As soon as I uncomment "" in the > example given > below, log4j is no longer picked up (by commons-logging). Is > there anything if it's working otherwise then make sure that you have all needed libraries in your classpath (mail.jar, activation.jar) > wrong with the configuration? There is

appender-ref to SMTPAppender knocks out log4j

As soon as I uncomment "" in the example given below, log4j is no longer picked up (by commons-logging). Is there anything wrong with the configuration? There is no error message or warning! http://jakarta.apache.org/log4j/";>

Re: Log4j xml configuration

On 2/14/07, Drinkwater, GJ (Glen) <[EMAIL PROTECTED]> wrote: Hi I am currently moving all our log4j.properties files to XML files and was wondering how I replicate this with the xml configuration. In the properties file, I can put in log4j.logger.my.package=DEBUG Which means only lo

Log4j xml configuration

Hi I am currently moving all our log4j.properties files to XML files and was wondering how I replicate this with the xml configuration. In the properties file, I can put in log4j.logger.my.package=DEBUG Which means only logs from 'my.package' with level DEBUG or above gets logged and anything

1.3alpha-8 question

We are looking at using the latest version of Chainsaw (version 2.0) in one of our projects. I noticed that it requires log4J version 1.3. Why is this still in alpha version and is there a release date for the final 1.3 version? Are there any problems or things I should know about given that i