cvs commit: jakarta-log4j/src/xdocs documentation.xml

ceki2003/02/27 22:36:24 Modified:src/xdocs documentation.xml Log: Fixed spelling. Revision ChangesPath 1.24 +1 -1 jakarta-log4j/src/xdocs/documentation.xml Index: documentation.xml ===

cvs commit: jakarta-log4j/src/xdocs documentation.xml

ceki2003/02/27 22:34:25 Modified:src/xdocs documentation.xml Log: Added links to a bunch of presentations provided by James Cakalic. Revision ChangesPath 1.23 +27 -9 jakarta-log4j/src/xdocs/documentation.xml Index: documentation.xml ===

RE: Reproducing the Apache license

> Moving to the Jalopy tool is a great thing. I almost forgot. Checkstyle too! -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Reproducing the Apache license

Thanks to Marco Hunsicker, the author of Jalopy, I was able to work out the header replacement/insertion issues. The "key" for the new and old header has to be comprised of unique text contained in each. Given the correct keys, Jalopy does a most excellent job of replacing the old header and not

cvs commit: jakarta-log4j/src/jalopy log4j-coding-convention.xml

mwomack 2003/02/27 21:10:59 Modified:src/jalopy log4j-coding-convention.xml Log: Updated version that removes old license header and inserts full Apache 1.1 License header. Revision ChangesPath 1.2 +14 -3 jakarta-log4j/src/jalopy/log4j-coding-convention.xml

cvs commit: jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet InitServlet.java InitContextListener.java CookieMDCFilter.java ConfigurationServlet.java

mwomack 2003/02/27 21:10:13 Modified:src/java/org/apache/log4j/servlet InitServlet.java InitContextListener.java CookieMDCFilter.java ConfigurationServlet.java Log: Versions with full Apache License 1.1 header. Revision Changes

cvs commit: jakarta-log4j-sandbox/src/java/org/apache/log4j/selector ContextJNDISelector.java ContextClassLoaderSelector.java

mwomack 2003/02/27 21:09:29 Modified:src/java/org/apache/log4j/selector ContextJNDISelector.java ContextClassLoaderSelector.java Log: Versions with full Apache License 1.1 header. Revision ChangesPath 1.3 +47 -55 jakarta-log4j-sandbox/src

cvs commit: jakarta-log4j-sandbox/src/jalopy log4j-coding-convention.xml

mwomack 2003/02/27 21:08:51 Modified:src/jalopy log4j-coding-convention.xml Log: Updated version that removes old license header and inserts full Apache 1.1 License header. Revision ChangesPath 1.2 +14 -3 jakarta-log4j-sandbox/src/jalopy/log4j-coding-convention

DO NOT REPLY [Bug 17511] - Patch for Chainsaw to utilise Receiver framework

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17511] - Patch for Chainsaw to utilise Receiver framework

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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17511] New: - Patch for Chainsaw to utilise Receiver framework

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://nagoya.apache.org/bugzilla/show_bu

RE: [Chainsaw] [PATCH] Current work so far

Attempt #2 with attached files: cheers, Paul Smith > -Original Message- > From: Paul Smith [mailto:[EMAIL PROTECTED] > Sent: Friday, 28 February 2003 9:41 AM > To: Log4j-Dev (E-mail) > Subject: [Chainsaw] [PATCH] Current work so far > > > Please find attached a patch file for existing

DO NOT REPLY [Bug 17507] - Priority does not override hashCode() method

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://nagoya.apache.org/bugzilla/show_bu

RE: [Chainsaw] [PATCH] Current work so far

bummer, did the .java and .xml file attachments get stripped? > -Original Message- > From: Paul Smith [mailto:[EMAIL PROTECTED] > Sent: Friday, 28 February 2003 9:41 AM > To: Log4j-Dev (E-mail) > Subject: [Chainsaw] [PATCH] Current work so far > > > Please find attached a patch file for

[Chainsaw] [PATCH] Current work so far

Please find attached a patch file for existing classes, plus some attachments for additional classes for Chainsaw, and the example log4j.xml file that can be used to start it using the Receiver model. I've verified that after the "jar" target has been run, Chainsaw can start on W2K using the follo

DO NOT REPLY [Bug 17507] - Priority does not override hashCode() method

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://nagoya.apache.org/bugzilla/show_bu

XML config issue & stacktrace

I am getting a stack trace with the following XML file (bearing in mind that the ChainsawAppender is a local class file at this point, it's actually the ConsoleAppender that's causing the issue as if I remove everything but that appender it still barfs): http://jakarta.apache.org/log4j/"; debug=

RE: [Chainsaw] ChainsawAppender: Chicken or the Egg Configuration

Paul, > > Can you just define -Dlog4j.configuration=[your file name > here] in the > > command line to start Chainsaw? Log4j will initialize itself > > using the > > file, which can contain the configuration for the reciever(s) and > > ChainsawAppender. > > *Doh*, forgot about the system prope

DO NOT REPLY [Bug 17507] New: - Priority does not override hashCode() method

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://nagoya.apache.org/bugzilla/show_bu

RE: [Chainsaw] ChainsawAppender: Chicken or the Egg Configuration

> I need to review PropertyConfigurator to see if we can modify > it to support > plugins. I think it is doable, just haven't had time to look at it. That would be neat although not essential. I wasn't sure if the Log4J community was moving forward to eventually disgarding the properties file.

RE: [Chainsaw] ChainsawAppender: Chicken or the Egg Configuration

Paul, > I've got the SocketReceiver stuff working, but found out that > the plugin > architecture can only be accessed via a log4j.xml config file > (it doesn't > load the plugin through PropertyConfigurator). Will this be > an issue in the > future? Be nice for PropertyConfigurator to be able

Enterprise logging...

We are a commercial software development company evaluating the suitability of log4j for our enterprise logging needs. With enterprise logging there are many issues to consider. Log4j is the most comprehensive solution I've seen so far. I'm sending this information to give the log4j group and un

DO NOT REPLY [Bug 17498] New: - Logging inconsistencies using DailyRollingFileAppender

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://nagoya.apache.org/bugzilla/show_bu

Re: Newbie question

Not sure I have understood your problem exactly, but you could use environment substitution in your properties/xml file. log4j.appender.XXX.filePath=T:\\LOG\${client_machine}.log ${client.machine} would need to have been set in the system properties before hand. At 12:04 PM 2/27/2003 +0100

Newbie question

Does anyone knows how I can specify dynamically the name of the file ? I sort of would like the following - Let Log4j use a property in my config file, likely "log4j.appender.XXX.filePath=T:\\LOG" - specify dynamically in my java classes wich filename to use. The reason is that I am currently devel

NtEventLogAppender modification

Hello, working with the NtEventLogAppender I posted yesterday I noticed that this version was a modification of the log4j 1.1.3 version. Now I have an modification of the log4j 1.2.8 version of the NtEventLogAppender.java that handles the problem of a not accessible NtEventLogAppender.dll. regard