Unit test needs good home

[Curt Arnold]

After porting the backslash stripping code back to log4cxx, I decided 
that I liked the stripDuplicateBackslashes better on FileAppender 
(where it is in log4cxx) than in OptionConverter and started to move it 
in my working copy of log4j.  However, I ran into the problem of not 
having a good home for the associated unit tests and abandoned that 
effort.

Unfortunately, I was coerced into doing a good thing when I 
unintentionally committed my modified FileAppender when removing 
DBAppender2.  At that point, I was compelled to remove the duplicate 
code from OptionConverter (I reverted it back to v 1.51) and change the 
unit test code in OptionSubstitutionTest to point to the new home in 
FileAppender.

I would have loved to move the unit test from OptionSubstitutionTest to 
a more appropriate home (for example, FileAppenderTestCase where it 
lives in the log4cxx test suite), however there does not seem to be a 
good home for simple unit tests.  All the test targets in the ant build 
appear to be related to some functional aspect of log4j.  Did I miss 
something or how about an "internal" test suite and associated ant 
target that would be the home for these types of tests.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]