On Mon, Mar 8, 2010 at 9:43 PM, Antoine Levy-Lambert <anto...@gmx.de> wrote:
> Clark Archer wrote: > > I've developed a new feature inspired by the old Eclipse JUnit Max plugin > > (no longer available). Taking the new FailureRecorder as an example, I > have > > coded up a HistoryRecorder which builds a simple text file containing a > > history of up to the last 100 executions for each test class/suite. I > track > > pass/fail and execution time for each test class and update the history > file > > at the end of each <junit /> task. > > > I am more worried by the need to fix bugs of existing tasks/types rather > than by a wish to add new features. > > I think if we add new features they should be very generic. That said, > your feature is interesting. > I have fiddled in my own project [not committed in the ant code base] > with a task which runs JUnit batches in parallel. > > > I'd be interested in bringing my code up to standard and contributing > this > > feature to Ant. Is there someone who would be willing to work with me as > a > > mentor on this? > > > I am currently very busy in my day job and right now my dream is to see > a few more bugs of Ant 1.8.0 fixed and release a 1.8.1. > > I don't mind working on bugs at all. So far most of my knowledge of ant internals is centered around the JUnitTask and JUnitTestRunner classes but I'm willing to learn. Are there any particular bugs to work on or should I just register for an account in the bug tracking system and try assigning one to myself? I also haven't been able to find Ant-specific coding standards/formatting rules (other than the Ant Ivy project). I'll take another look. Thanks, -Clark A.
