Compelling Reasons to adopt log4j2

2007-04-17 Thread Paul Smith
I got stuck, and all I can think of are these. Other people may want to look at this and think about what might compel them to switch to log4j2 (when we get there.. :) ) Compelling Reasons for a log4j2 adoption * Ease of migration/Drop in replacement for log4j 1.2 - If we do not meet

Re: Chainsaw dependencies on log4j 1.3

2007-04-17 Thread Paul Smith
On 17/04/2007, at 4:38 PM, Curt Arnold wrote: On Apr 17, 2007, at 12:14 AM, Paul Smith wrote: Curt, many thanks for your efforts to get this this far. I've followed the below steps, and it's _almost_ working. I think the Receivers module will need to have a copy of

Re: Compelling Reasons to adopt log4j2

2007-04-17 Thread Curt Arnold
On Apr 17, 2007, at 1:16 AM, Paul Smith wrote: I got stuck, and all I can think of are these. Other people may want to look at this and think about what might compel them to switch to log4j2 (when we get there.. :) ) Compelling Reasons for a log4j2 adoption * Ease of migration/Drop in

Re: Chainsaw dependencies on log4j 1.3

2007-04-17 Thread Curt Arnold
On Apr 17, 2007, at 1:55 AM, Paul Smith wrote: On 17/04/2007, at 4:38 PM, Curt Arnold wrote: On Apr 17, 2007, at 12:14 AM, Paul Smith wrote: Curt, many thanks for your efforts to get this this far. I've followed the below steps, and it's _almost_ working. I think the Receivers module

Re: Chainsaw dependencies on log4j 1.3

2007-04-17 Thread Paul Smith
The ant build.xml can has a 'webstart-dist' target and an 'iOrb' type target. They generate and sign the jar files (it prompts you for a local keystore and certificate passwords during the signing process; I have my thawte certificate loaded in a keystore locally). I think I had a

GSOC: Congratulations Isuru (?)

2007-04-17 Thread Paul Smith
Unless I've misread something on the Google groups, Isuru Suriarachchi and his 'Adding Functionality and Usability Improvements to Chainsaw' project has been accepted as a GSOC project. (it has, at least been marked as 'slotted'. Not exactly sure what that means) If this is the case;

DO NOT REPLY [Bug 42148] - PropertyConfigurator.configure() does not close properties file

2007-04-17 Thread bugzilla
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=42148. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 42148] New: - PropertyConfigurator.configure() does not close properties file

2007-04-17 Thread bugzilla
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=42148. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 40944] - PropertyConfigurator.configure( URL ) does not close the resource stream

2007-04-17 Thread bugzilla
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=40944. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Re: Chainsaw dependencies on log4j 1.3

2007-04-17 Thread Curt Arnold
On Apr 17, 2007, at 5:27 AM, Paul Smith wrote: The ant build.xml can has a 'webstart-dist' target and an 'iOrb' type target. They generate and sign the jar files (it prompts you for a local keystore and certificate passwords during the signing process; I have my thawte certificate

Re: GSOC: Congratulations Isuru (?)

2007-04-17 Thread Isuru Suriarachchi
Hi Paul and Scott, Yes you are correct. My project has been selected as a GSoC project. Thanks very much for your help so far. I think I'll need more help when the project will be started. :-) Coding will be started on 28th of May according to the GSoC time line. These days we are on a short

svn commit: r529788 - /logging/sandbox/log4j/receivers/src/main/java/org/apache/log4j/varia/LogFilePatternReceiver.java

2007-04-17 Thread psmith
Author: psmith Date: Tue Apr 17 15:09:54 2007 New Revision: 529788 URL: http://svn.apache.org/viewvc?view=revrev=529788 Log: Coping log4j trunk (1.3) version of LogFilePatternReceiver.java over to sandbox receiver area in readiness for combining with Chainsaw. Added:

svn commit: r529789 - /logging/sandbox/log4j/receivers/src/main/java/org/apache/log4j/varia/LogFilePatternReceiverBeanInfo.java

2007-04-17 Thread psmith
Author: psmith Date: Tue Apr 17 15:10:49 2007 New Revision: 529789 URL: http://svn.apache.org/viewvc?view=revrev=529789 Log: Coping log4j trunk (1.3) version of LogFilePatternReceiverBeanInfo.java over to sandbox receiver area in readiness for combining with Chainsaw. Added:

svn commit: r529792 - in /logging/sandbox/log4j/receivers: pom.xml src/main/java/org/apache/log4j/varia/LogFilePatternReceiver.java

2007-04-17 Thread psmith
Author: psmith Date: Tue Apr 17 15:19:31 2007 New Revision: 529792 URL: http://svn.apache.org/viewvc?view=revrev=529792 Log: * Fixed up LoggingEvent constructor usage to comply with log4j 1.2. * Changed pom.xml to reference expression-filter project due to the LogFilePatternRecevier dependency

Re: Chainsaw dependencies on log4j 1.3

2007-04-17 Thread Paul Smith
On 17/04/2007, at 4:38 PM, Curt Arnold wrote: On Apr 17, 2007, at 12:14 AM, Paul Smith wrote: Curt, many thanks for your efforts to get this this far. I've followed the below steps, and it's _almost_ working. I think the Receivers module will need to have a copy of

maven and jms

2007-04-17 Thread Paul Smith
Ok, I tried adding the jms dependency to the receivers pom.xml, but try as I might to fight with the maven settings.xml I continually get this error: Missing: -- 1) javax.jms:jms:jar:1.1 Try downloading the file manually from the project website. Then, install it using the

Re: maven and jms

2007-04-17 Thread Curt Arnold
On Apr 17, 2007, at 5:52 PM, Paul Smith wrote: Ok, I tried adding the jms dependency to the receivers pom.xml, but try as I might to fight with the maven settings.xml I continually get this error: Missing: -- 1) javax.jms:jms:jar:1.1 Try downloading the file manually from the

Re: maven and jms

2007-04-17 Thread Paul Smith
ok, so I literally do just follow those directions. Cool, just thought it was odd. Thanks Curt. On 18/04/2007, at 9:14 AM, Curt Arnold wrote: On Apr 17, 2007, at 5:52 PM, Paul Smith wrote: Ok, I tried adding the jms dependency to the receivers pom.xml, but try as I might to fight with

[Patch review please] Further work for Receivers backport to 1.2

2007-04-17 Thread Paul Smith
Hi all, I've completed porting the remaining Receiver classes to the sandbox area. The below patch is what I have locally, and taking the generated jar and adding it as a dependency to Chainsaw makes everything compile nicely. I am not able to do any testing on this as yet, and figure

Re: Chainsaw dependencies on log4j 1.3

2007-04-17 Thread Paul Smith
The WebStart model appears to use X.509 certificates which route back to a Certificate Authority, hence dealing with Thawte signatories. Doesn't seem to be any bridge between the GPG model and the X.509 model which would allow us to use our existing GPG code signing keys. The keys are

Re: [Patch review please] Further work for Receivers backport to 1.2

2007-04-17 Thread Curt Arnold
On Apr 17, 2007, at 10:42 PM, Paul Smith wrote: Hi all, I've completed porting the remaining Receiver classes to the sandbox area. The below patch is what I have locally, and taking the generated jar and adding it as a dependency to Chainsaw makes everything compile nicely. I am not

Re: [Patch review please] Further work for Receivers backport to 1.2

2007-04-17 Thread Curt Arnold
On Apr 17, 2007, at 11:27 PM, Curt Arnold wrote: On Apr 17, 2007, at 10:42 PM, Paul Smith wrote: Hi all, I've completed porting the remaining Receiver classes to the sandbox area. The below patch is what I have locally, and taking the generated jar and adding it as a dependency to

RE: [Patch review please] Further work for Receivers backport to 1.2

2007-04-17 Thread Scott Deboy
In DBAppender: insertStatement.setLong(0, 0); should be insertStatement.setLong(1, 0); Also, in CustomSQLDBReceiver: Should LoggingEvent event = new LoggingEvent(null, eventLogger, timeStamp, levelImpl, message, threadName, throwableInfo, ndc, locationInfo, properties); be LoggingEvent event =