On Thu, 2004-10-07 at 13:17, Dominique Devienne wrote: > 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.
Sure, that makes sense. Perhaps the right answer is for JUnitTestRunner to report test count, start and end via new methods in the JUnitResultFormatter interface, which the current implementors can ignore so their output isn't changed. Our IDE could then use its own formatter. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
