; Michael Dunn
Subject: RE: Loose logging when using forkmode
Neal
does your log4j.properties contain log4j.appender.STDOUT.follow=true
# need to set follow for stdout as it gets moved around in junit tests
log4j.appender.STDOUT.follow=true
as suggested by pete in Bugzilla
https://issues.apache.org
recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Mon, 6 Oct 2008 18:05:09 -0400
> From: [EMAIL PROTECTED]
> Subject: Loose logging when using forkmode
> To: user@ant.apache.org
> CC: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [
Environment: ant 1.7.1, junit4.4
We lost log4j logging output (eg. log.debug) in the section
of the XML files when we switched to perBatch forkmode. [perBatch
forkmode helps us greatly with performance of the tests.] Actually, the
FIRST test case that runs includes the log4j logging output bu
