Yet another release candidate

I've posted an log4j 1.2.12 release candidate log4j-1.2.12rc4 to http://people.apache.org/~carnold/logging-log4j-1.2.12rc4.zip and http://people.apache.org/~carnold/logging-log4j-1.2.12rc4.tar.gz. This is not explicitly not an official release and should not be used for anything other than

cvs commit: logging-log4j/docs HISTORY.txt

carnold 2005/08/19 17:58:48 Modified:.Tag: v1_2-branch build.xml docs Tag: v1_2-branch HISTORY.txt Log: Bug 36283: Change build and HISTORY in anticipation of log4j 1.2.12 release next week Revision ChangesPath No revision N

DO NOT REPLY [Bug 36283] New: - log4j 1.2.12 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

DO NOT REPLY [Bug 36268] - Add "release" target to build.xml to specify stricter build for public releases

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/tests run-tests.bat

carnold 2005/08/19 17:50:23 Modified:testsTag: v1_2-branch run-tests.bat Log: Add JDK 1.1 compatible test compilation Revision ChangesPath No revision No revision 1.1.2.2 +47 -1 logging-log4j/tests/Attic/run-tests.bat

cvs commit: logging-log4j/tests run-tests.bat

carnold 2005/08/19 14:08:42 Added: testsTag: v1_2-branch run-tests.bat Log: Add batch file for running subset of tests on JDK 1.1 Revision ChangesPath No revision No revision 1.1.2.1 +36 -0 logging-log4j/tests/Attic/run-

DO NOT REPLY [Bug 36282] - ConsoleAppender ignores encoding set with setEncoding()

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 36282] New: - ConsoleAppender ignores encoding set with setEncoding()

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/tests/src/java/org/apache/log4j/xml DOMTestCase.java

carnold 2005/08/19 12:35:09 Modified:tests/src/java/org/apache/log4j Tag: v1_2-branch LoggerTestCase.java MinimumTestCase.java PatternLayoutTestCase.java tests/src/java/org/apache/log4j/net Tag: v1_2-branch

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/spi LoggingEventTest.java

carnold 2005/08/19 12:33:38 Modified:tests/src/java/org/apache/log4j/spi Tag: v1_2-branch LoggingEventTest.java Log: Bug 26433: Relax serialization tests for JDK 1.1 Revision ChangesPath No revision No revision

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

carnold 2005/08/19 12:30:30 Modified:src/java/org/apache/log4j Tag: v1_2-branch FileAppender.java src/java/org/apache/log4j/spi Tag: v1_2-branch LoggerRepository.java Log: Bug 9150: Check for null return from getParent when creating dir Rev

Re: 1.2.12 Experimental Build

On Aug 19, 2005, at 6:34 AM, Endre Stølsvik wrote: Have you tested by using the normal javac (thus 1.5), but with bootclasspath set (and -obviously- target=1.1|2)? I find this better, as one may assume that later javac's will make more efficient code than earlier (using the bytecode better, t

Re: log4j 1.2.12 on JDK 1.[2|3|4|5]

| If you use -classpath, it appears to not locate the core JDK | classes which is likely a long forgotten feature/bug on JDK 1.1. You -had- to set the classpath on those, including the rt.jar. Feature. It is the later ones that find the bootclasspath itself. That's why a "bootclasspath" param w

Re: 1.2.12 Experimental Build

On Wed, 17 Aug 2005, Mark Womack wrote: | I got a chance to play with the 1.2 build tonight. Here is what I did: Very good work! | | 1) Isolated the build jdk from the Ant runtime jdk. | | Basically, I added the following attributes to all of the javac tasks: | | fork="yes" |

Re: 1.2.12 Experimental Build

On Thu, 18 Aug 2005, Curt Arnold wrote: | | For example, anyone who had used "ant -Dbuild.compiler=gcj" to build log4j | using GCJ would now have his specification overridden. You do know that earlier set variables won't be overridden when (tried) set again, right? This means that having some in

log4j 1.2.12 on JDK 1.[2|3|4|5]

As you can tell, been busy today. In the current state, log4j should build and pass all unit tests on JDK 1.2-5 (that is building and running on same JDK, haven't tested crosses yet). JDK 1.2 will require you to rebuild Ant 1.6.5 first since it suffers from the same issue that we have bee

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/xml DOMTestCase.java

carnold 2005/08/19 00:10:23 Modified:testsTag: v1_2-branch build.properties.sample build.xml tests/src/java/org/apache/log4j Tag: v1_2-branch MinimumTestCase.java PatternLayoutTestCase.java tests/src/java/org/apache/log4j/net Tag:

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/util SerializationTestHelper.java

carnold 2005/08/19 00:09:39 Modified:tests/src/java/org/apache/log4j/spi Tag: v1_2-branch LoggingEventTest.java tests/src/java/org/apache/log4j/util Tag: v1_2-branch SerializationTestHelper.java Log: Bug 26433: Relax seri