----- Original Message -----
From: "Thomas Tuft Muller" <[EMAIL PROTECTED]>
> I guess one way to do it is to configure a new Java process with the
> DOMConfigurator/logfj.xml and check if any errors are submitted to std
err.
Does the DOMConfigurator throw exceptions? If so, you could just wrap it
inside a JUnit test case and use the <junit> task to deal with it
(haltonfailure="true" even!). Even without exceptions, if there is
something you can check for perhaps a JUnit test is still a good thing. Or
a custom Ant task (which should live in the Log4j codebase, I'd think) would
be even more easily re-usable by others.
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
