DO NOT REPLY [Bug 22894] - Single backslash not accepted in File param value

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

cvs commit: logging-log4j/tests/input/db append-with-jndi1.xml read-with-pooled-datasource1.xml read-with-datasource1.xml

ceki2005/02/11 05:13:18 Modified:tests/input/db append-with-jndi1.xml read-with-pooled-datasource1.xml read-with-datasource1.xml Log: small fixes Revision ChangesPath 1.5 +5 -4

cvs commit: logging-log4j/tests ugli-test.xml

ceki2005/02/11 06:45:51 Modified:testsugli-test.xml Log: minor fix Revision ChangesPath 1.4 +1 -1 logging-log4j/tests/ugli-test.xml Index: ugli-test.xml === RCS file:

cvs commit: logging-log4j .cvsignore

ceki2005/02/11 08:52:02 Modified:..cvsignore Log: CVS ignore whatever is in tmp/ Revision ChangesPath 1.16 +1 -0 logging-log4j/.cvsignore Index: .cvsignore === RCS file:

Message based rolling trigger

I had what seemed like a reasonable request from one of my client to have a way to programatically initiate a rollover. What I think would work well would be to modify the signature for TriggeringPolicy.isTriggeringEvent to include the event in addition to the file and to add a

Re: Message based rolling trigger

No objections from me. I've heard of rollovers based on date and size but never on message contents. I am curious about the use case. At 06:30 PM 2/11/2005, Curt Arnold wrote: What I think would work well would be to modify the signature for TriggeringPolicy.isTriggeringEvent to include the

Re: Message based rolling trigger

On Saturday 12 February 2005 01:38, Ceki Gülcü wrote: No objections from me. I've heard of rollovers based on date and size but never on message contents. I am curious about the use case. I can think of one from the Process Control industry; A lot of Process Control is operating around

cvs commit: logging-log4j/tests/witness/xml dom.A1.2 dom.A2.2

carnold 2005/02/11 10:11:44 Modified:src/java/org/apache/log4j FileAppender.java PatternLayout.java src/java/org/apache/log4j/helpers OptionConverter.java src/java/org/apache/log4j/joran/action ParamAction.java

DO NOT REPLY [Bug 22894] - Single backslash not accepted in File param value

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

DO NOT REPLY [Bug 22894] - Single backslash not accepted in File param value

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

Re: DBAppender2?

Have you considered using Apache Derby (http://incubator.apache.org/derby/) in the tests? Just a question, not a recommendation. I know it would add yet another dependency to the build (and an incubated one at that), but it should allow you to test against a real database without a lot of

Re: DBAppender2?

No doubt that DBAppender should support Derby. Having a lightweight DB is certainly the way to go for testing purposes. Has anyone already used mock objects to fake JDBC connection failures? At 09:17 PM 2/11/2005, you wrote: Have you considered using Apache Derby

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/helpers OptionSubstitutionTest.java

carnold 2005/02/11 13:17:11 Modified:src/java/org/apache/log4j/helpers OptionConverter.java tests/src/java/org/apache/log4j/helpers OptionSubstitutionTest.java Log: bug 22894: Backslashes in file specs, UNC handling Revision Changes

cvs commit: logging-log4j/src/java/org/apache/log4j/db DBAppender2.java

carnold 2005/02/11 15:14:35 Modified:src/java/org/apache/log4j FileAppender.java Removed: src/java/org/apache/log4j/db DBAppender2.java Log: Removing unused DBAppender2 Revision ChangesPath 1.49 +40 -1

cvs commit: logging-log4j/src/java/org/apache/log4j/helpers OptionConverter.java

carnold 2005/02/11 15:33:51 Modified:src/java/org/apache/log4j/helpers OptionConverter.java Log: Bug 22894(Backslashes): moving strip method to FileAppender, reverting OptionConverter Revision ChangesPath 1.54 +0 -41

DO NOT REPLY [Bug 33531] New: - New feature: Event filter based rolling

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

cvs commit: logging-log4j/src log4j-coding-convention.xml

carnold 2005/02/11 19:06:59 Modified:src log4j-coding-convention.xml Log: Updating code conventions for 2005 Revision ChangesPath 1.2 +1 -1 logging-log4j/src/log4j-coding-convention.xml Index: log4j-coding-convention.xml

Filter based triggering policy

I've committed org.apache.log4j.rolling.FilterBasedTriggeringPolicy and associated tests as bug 33531. The policy will evaluate the current message against a set of filters and if the message passes the filters, a rollover is initiated. The associate test is pretty contrived, it triggers on