robert burrell donkin wrote:
i'd guess that commons-logging is not picking up log4j and is defaulting to printing to system out which is being swallowed by the junit task. i can't remember off-hand how to make ant/junit log to console but you should be able to find out by reading the manual and searching the web. if my guess is right, once you do this you'll see the messages.
BTW make sure you log to error since (when commons-logging is misconfigured, it's likely that low level messages will be ignored).
Thanks for the help. As it turns out, commons-logging found a log4j.properties in xdoclet-1.2.1.jar before finding my log4j.properties file. I rearranged the classpath a bit and it's working as expected.
- Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
