CVS problem!

I tried updating Log4j HEAD a couple times and got the following errors... 1. cannot mkdir /tmp/cvs-serv28896/contribs No space left on device Error, CVS operation failed (exit code 1) 2. cannot open /tmp/cvs-serv28940/./CVS/Repository No space left on device Error, CVS operation failed (exit

DO NOT REPLY [Bug 35748] New: - Use of read/write lock acquisition not necessarily safe in Category

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

DO NOT REPLY [Bug 24159] - Log4J can create deadlock conditions

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: Bug #24159

On Thu, 2005-07-14 at 17:25 -0500, Curt Arnold wrote: > > I agree that it is too potentially disruptive to attempt in 1.2.x. > I'm not ready to commit to doing it in 1.3, however. log4j currently > does fairly coarse synchronization which has been raised as an issue > repeatedly (the whole

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

carnold 2005/07/14 17:07:00 Modified:src/java/org/apache/log4j Tag: v1_2-branch ConsoleAppender.java Log: Bug 31056: Restore final closeWriter on 1.2 branch Revision ChangesPath No revision No revision 1.12.2

cvs commit: logging-log4j build.xml

carnold 2005/07/14 16:51:37 Modified:.Tag: v1_2-branch build.xml Log: Bug 35516: Add jdiff target to build.xml on 1.2 branch Revision ChangesPath No revision No revision 1.34.2.23 +24 -3 logging-log4j/build.xml Inde

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

carnold 2005/07/14 16:43:32 Modified:src/java/org/apache/log4j ConsoleAppender.java Log: Bug 31056: Restore final closeWriter Revision ChangesPath 1.25 +10 -0 logging-log4j/src/java/org/apache/log4j/ConsoleAppender.java Index: ConsoleAppender.java ===

Re: Bug #24159

On Jul 14, 2005, at 5:01 PM, Paul Smith wrote: That is a biggie isn't it... I feel quite a bit uncomfortable about attempting this for 1.2.x. My rationale is that 1.2.x has been around a LONG time now. I know "better the devil you know" is not a great way to develop software, but in th

RE: Bug #24159

Hey, I couldn't have said it better than Paul: I agree with everything he says. This is not a good 1.2 candidate, but should be a requirement for 1.3.0. Yoav Shapira System Design and Management Fellow MIT Sloan School of Management / School of Engineering Cambridge, MA USA [EMAIL PROTECTED] / [EM

Re: Bug #24159

That is a biggie isn't it... I feel quite a bit uncomfortable about attempting this for 1.2.x. My rationale is that 1.2.x has been around a LONG time now. I know "better the devil you know" is not a great way to develop software, but in this case I think we may end up creating more proble

DO NOT REPLY [Bug 23705] - Parser get confused when using external entities.

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

Bug #24159

Does anyone want to weigh in on this bug? Besides adding TRACE, it looks like this is the most controversial bug fix. http://issues.apache.org/bugzilla/show_bug.cgi?id=24159 -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] Fo

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

carnold 2005/07/14 14:28:27 Modified:tests/src/java/org/apache/log4j/xml DOMTest.java Added: tests/input/xml DOMTest4.xml DOMTest4_A1.xml DOMTest4_A2.xml tests/witness/xml dom.A1.4 dom.A2.4 Log: Bug 23705: Add external entity test to log4j CVS HEAD Revisio

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

carnold 2005/07/14 14:23:55 Modified:src/java/org/apache/log4j/xml Tag: v1_2-branch DOMConfigurator.java tests/src/java/org/apache/log4j/xml Tag: v1_2-branch DOMTestCase.java Added: tests/input/xml Tag: v1_2-branch DO

DO NOT REPLY [Bug 31056] - (PATCH) Console appender doesn't notice changes to System.out/System.err

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

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

carnold 2005/07/14 12:31:52 Modified:src/java/org/apache/log4j Tag: v1_2-branch ConsoleAppender.java Log: Bug 31056: Apply fix to v1.2 branch Revision ChangesPath No revision No revision 1.12.2.3 +89 -28

cvs commit: logging-log4j/src/xdocs/stylesheets project.xml

sdeboy 2005/07/14 10:40:31 Modified:src/xdocs/stylesheets project.xml Log: Re-add chainsaw link Revision ChangesPath 1.27 +1 -0 logging-log4j/src/xdocs/stylesheets/project.xml Index: project.xml ===

RE: Chainsaw link gone from log4j page

I'll add it back. -Original Message- From: Mark Womack [mailto:[EMAIL PROTECTED] Sent: Thu 7/14/2005 10:14 AM To: 'Log4J Developers List' Cc: Subject:RE: Chainsaw link gone from log4j page I might have done that. I was reviewing stuff some time back, and the link tha

RE: Chainsaw link gone from log4j page

I might have done that. I was reviewing stuff some time back, and the link that was there did not seem to be valid or went to a page that was bogus. Also, when I reviewed stuff for the 1.2.11 release, the docs that were in the 1.2 branch were this strange mix of 1.2/1.3 pages. I modified them to

Chainsaw link gone from log4j page

Someone changed the log4j page and removed the Chainsaw link from the navigation bar. I can't find a place that provides a link to Chainsaw, so I'd like to see some navigation re-added. Is there a reason why it was removed? Scott <>

DO NOT REPLY [Bug 35743] New: - SyslogAppender throws a NullPointerException upon misconfiguration

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