Andreas Korneliussen wrote:
If this sounds acceptable, I can try to get this to work with the derby
test harness and (if successful) provide a patch for it.
I think this sounds acceptable, for solving the useprocess problem. I do
however think writing a new TestRunner class could be very useful, not
only for solving this specific issue. So, if you do not want to make a
new TestRunner class now, I may do so later.
I see your point. I do not have any intentions to write a new TestRunner
class at this time. So unless you are going to submit such a class "very
soon", I might go ahead and implement what I described in the meantime (as a
way of learning a bit more about JUnit).
--
John
