DO NOT REPLY [Bug 35032] - Blocking issues for log4j 1.2.11 release

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

1.2.11rc3 build

The 1.2.11rc3 build is available at: http://people.apache.org/~mwomack/log4j-1.2.11rc3/ I believe that I have done as much as I can do for issue #8 without some major changes to the build file etc. This build is at least as good as previous 1.2.X builds. I have run all of the unit tests unde

cvs commit: logging-log4j build.xml

mwomack 2005/06/02 22:31:33 Modified:.Tag: v1_2-branch build.xml Log: Officially moving to 1.2.11rc3 for version number. Revision ChangesPath No revision No revision 1.34.2.21 +1 -1 logging-log4j/build.xml Index: b

RE: JUnit Errors in 1.2.11 build

Thanks, Ceki. I'll give it try in the 1.3 jvm I installed last night to make sure it at least passes the tests someplace. How do you test the 1.2 release under jvm 1.1/1.2 to make sure it is happy there? Do you just hand-run some custom exe to make sure it comes up and runs, etc? I don't think

RE: JUnit Errors in 1.2.11 build

Missed your first message with the output. If my memory serves me correctly, immunity to the jvm's reflection implementation was added in log4j 1.3. The tests for 1.2 need to be run on JDK 1.3. Alternatively, you can retrofit the immunity granting code from the 1.3 branch. At 06:37 PM 6/2/20

RE: JUnit Errors in 1.2.11 build

Mark, The tests are supposed to be immune to variations in reflection implementation. Do you have the output of the failed test? At 06:31 PM 6/2/2005, Mark Womack wrote: Ant 1.6.4, jvm Sun 1.4.2_07 (though I think _06 has the same issue). I think I am using junit 1.3.8, but since there are

RE: JUnit Errors in 1.2.11 build

Ant 1.6.4, jvm Sun 1.4.2_07 (though I think _06 has the same issue). I think I am using junit 1.3.8, but since there are no identifying marks in the .jar file (annoying), it is hard to tell exactly. I agree that the exact stack trace is going to be fragile, left to the whims of the jvm reflection

Re: JUnit Errors in 1.2.11 build

Curt Arnold wrote: On Jun 2, 2005, at 12:33 AM, Mark Womack wrote: I am running the test cases against the 1.2.11 code, and the minimum case fails right off the bat: Minimum: [junit] Running org.apache.log4j.MinimumTestCase [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed:

DO NOT REPLY [Bug 35180] New: - Multiple lines "XML files (*.xml)" in drop down list "Files of type"

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: WriterAppender does not read Encoding configuration value from file

Oops. Sorry. Wrond address =) -- Slava Tutushkin, http://aloner.ru mailto:[EMAIL PROTECTED] ICQ: 55463183 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

WriterAppender does not read Encoding configuration value from file

Hi all. I was trying to create unicode logs and messed with it for whole night. As it turned out, there is no setOption method in WriterAppender, so it was impossible to get Unicode output just with using PropertyConfigurator. And what is more, doing setEncoding after reading config