> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > On Mon, 09 Feb 2004, Mariano Benitez <[EMAIL PROTECTED]> wrote: > > The problem is that I cannot simulate this using JUnit with > > fork, because I cannot change the main class and use mine > > instead. > > I assume that your class understands all the command line arguments > Ant's testrunner uses and passes them along. How would your class > deal with new arguments we add? > > The main problem with opening up access to the test runner class is > just that. As soon as we do it, we run the risk of breaking other > people's builds when we change the protocol between the task and the > test runner. There is no danger now, as we always know the main class > that gets invoked.
The solution would be to make the Ant test runner public and extensible, so that people that need to extend it, for example to run all the tests in a single forked VM instead of the super slow forking for every test current mode, can do so. The current approach is too much a closed-system. BTW, the patch submitted against Ant 1.5.x to allow forking once was never incorporated. When I tested this patch, the <junit> tasks is 7x faster! Starting up a new VM for every single tests just ain't efficient enough. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
