logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: to-do list
Date Sun, 17 Apr 2005 18:43:11 GMT

At 08:33 PM 4/15/2005, you wrote:
>I've been distracted from log4j for a while by log4cxx and more recently 
>tax preparation.  I hope to be able to spend devote some time to log4j in 
>the near future.  In my working copy I have a couple of new tests that I 
>expect to commit before I start anything new:
>EncodingTest was written primarily to support the implementation of 
>WriterAppender.encoding in log4cxx.  The code under test in log4j is 
>fairly trivial, essentially the getters and setters, since encoding itself 
>is handled by java.io.Writer.  However, the code under test in log4cxx is 
>fairly substantial and I really like having similar tests in log4j and log4cxx.

Why? log4cxx and log4j are distinct code bases. As far as I know, you are 
the only person who looks at both. If the implementation of a particular 
feature is done differently in log4j and log4cxx, then why should the test 
cases need to be similar?

>LoggingEventTest primarily checks the serialization of LoggingEvent's 
>against reference copies.  I expect these tests to evolve as I get into 
>the whole sequenceCount issue.  However, at the present they do serve as a 
>check against unintended changes in the serialized form.
>I'd like to get these in before the switch to Subversion, so please let me 
>know when that is imminent.

The migration to subversion should take place in the very near future. So 
it should be considered imminent.

>After I get back into it, the following log4j-related things seem to be at 
>the top of my list:
>Port o.a.l.r.RollingFileAppender to log4cxx.  I expect that to be fairly 
>clean but might suggest some changes to log4j.
>Port JoranConfigurator to log4cxx.  I expect that this will suggest some 
>changes to the log4j implementation.
>Review the LoggingEvent related issues (sequenceCount and serialization).
>I have the sneaking suspicion that XMLLayout may not handle some edge 
>cases and will want to work up some tests to confirm it.

Ceki Gülcü

   The complete log4j manual: http://www.qos.ch/log4j/

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message