The latest version of LoggingEvent includes commentary, a fix of a forward compatibility bug (not reading unexpected primitives), and a switch statement in the place of an if(char) else if (char).
http://traxel.com/java/log4j/LoggingEvent.java On Sun, 2 Dec 2001, Robert Bushman wrote: > In reading this post, I find it very confusing. > A simpler explanation is: > > 1. Compile all three classes and add them to your 1.2 jar file. > 2. Create a jar containing *only* UnitTestLoggingEvent.class > called "unit-test.jar". > 3. export CLASSPATH=unit-test.jar:junit.jar > NOTE: Do not add "." or log4j.jar to your classpath. > 4. java org.apache.log4j.test.UnitTestLoggingEvent > > > On Sun, 2 Dec 2001, Robert Bushman wrote: > > > Hi, > > > > Here's the latest source for the version safe LogginEvent > > and the unit test. > > > > http://traxel.com/java/log4j/ > > > > You'll also need UnitTestProxy.java, which has to be > > included in the jar with the current version of Log4j. > > > > You must have a copy of UnitTestLoggingEvent.class in > > a seperate directory or jar file from everything else > > for the test to work. Set your classpath to junit.jar > > and the structure that contains UnitTestLoggingEvent > > all by itself, and you're ready to run. > > > > Bob > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > ------------------------------------------------------------------- Who owns your data? Proprietary protocols and file formats are dangerous. ------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
