> From: Tom Ball [mailto:[EMAIL PROTECTED] > > 1. (Preferred) Log sub-informational messages for these events, which a > BuildListener could filter. The problem is that while the JUnitTask > logs events, its JUnitTestRunner does not (everything goes to stdout and > stderr). JUnitTestRunner is completely decoupled from Ant, except for > using a few static and utility methods.
And I believe the reason it's completely decoupled is because of <junit fork="true">. This allows unit testing Java code which depends on native code, and also to avoid Ant's classpath messing up the tests' classpath. For this reason, JUnitTestRunner has to be as stand-alone as possible, and Ant injects just enough of itself classpath-wise so that JUnitTestRunner has all it needs, in addition to the user-specified classpath. Logging events back to the parent Ant VM would require cross-process/VM communication in the listener, which was never implemented. Doesn't answer your question, but hopefully provides a little context. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
