I made a change to the patch to append log4j messages from the code under test to a file in the output directory.
This substantially reduces the output to stdout, but there are still a few issues that need to be resolved, cancelling
1) I'm consistently seeing 6 failures, all of the FLE/LE/HierQu tests, but acl tests are failing as well
2) all tests running under a single VM may be a problem for us. Our server is really designed to shutdown
via exiting the vm, not necessarily cleaning up every detail. Having this expectation in the tests may be
unrealistic, at least from the perspective of easily converting to testng.
The updated patch also included a small set of changes to output interceptor.
I'm thinking that it might be interesting to look at having ant fork each test class, running testng as the forked
process. This target can run all the classes, and subsequently check if any failed and return failure if any one
test fails. (this is essentially what junit task does in ant with forkmode=pertest). I'm surprised testng does not
support this. (ant "apply" task can do the looping over test classes btw)