DO NOT REPLY [Bug 31736] - DailyRollingFileAppender rollover part of logs with wrong log time.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: Yet another Apender proposal: ListAppender

> In fact, what I (beeing a log4j user) needed was exactly an Appender. I > needed it, to feed it directly to the Logger.addApender(Appender) > method. The CyclicBuffer wouldn't help here, cause it doesn't implement > the Apender interface. So anyway I'd have to write my own appender. > > On the ot

cvs commit: logging-log4j/docs HISTORY

psmith 2004/10/18 15:24:58 Modified:docs HISTORY Log: Added blurb about the ListAppender & ListModelAppender. Note: I am assuming this is 100% backward compatible. Can't see why it wouldn't be. Revision ChangesPath 1.116 +5 -0 logging-log4j/docs/HISTO

cvs commit: logging-log4j/src/java/org/apache/log4j/varia ListAppender.java ListModelAppender.java

psmith 2004/10/18 15:16:35 Modified:src/java/org/apache/log4j/chainsaw/messages MessageCenter.java Added: src/java/org/apache/log4j/varia ListAppender.java ListModelAppender.java Removed: src/java/org/apache/log4j/chainsaw/me

RE: Please remove "enum" as variable name.

Hi, This has already been fixed on CVS HEAD (a while ago), so log4j 1.3 alpha should be fine. As for log4j 1.2, you can use the source="1.4" javac compiler switch to make it build on J2SE 5.0. If someone has a lot of free time and thinks this is worthwhile, they can go back in CVS on the 1.2 bra

Please remove "enum" as variable name.

We have started to trial with JDK1.5 in Gump. It won't be soon for it to become the official build platform, nor nagging you about it. However, I think it is time to slowly reporting problems found, to the respective camps, for them to take a look at it. http://brutus.apache.org/gump/jdk15/log

Re: Yet another Apender proposal: ListAppender

Hi Michael, Joran also requires a buffer type appender to collect logging events that it generates while configuring the log4j environment. Once the config file is parsed, it instructs the buffer to forward the collected events in the new environment. This sounds similar to the motivation you ha

Re: Yet another Apender proposal: ListAppender

Hi. Everything new is old again (or vice versa) ;) Of course. I didn't claim that ListAppender was something new and magic. I just thought it was another piece which would probably fit well into the puzzle. This has been available forever in the form of the CyclicBuffer, used by the SMTPAppender a

RE: Yet another Apender proposal: ListAppender

Hi, Everything new is old again (or vice versa) ;) This has been available forever in the form of the CyclicBuffer, used by the SMTPAppender among others. You don't need a whole new Appender just for this. Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Paul Smith [

Re: Yet another Apender proposal: ListAppender

Hello Paul. Thanks for your answers. I'm glad to see, that the concept of storing LoggingEvents is not too uncommon. However, the two implementations you found are neither documented in the API docs on the website, nor are they contained in the distribution jars. (At least they are not in the l