@Michael: I'll fork your repo then to continue work on that. I actually got interested in Ant finally due to build troubles at my job. We've got two separate build systems on one of our largest projects: a terribly written ant build, and a terribly slow gradle build. I've taken over rewriting the ant build, and in the process, I ended up rewriting an antlib we were using which got me further into Ant internals. I couldn't get into gradle or maven, but ant was actually understandable!
On 31 March 2014 20:46, Antoine Levy Lambert <anto...@gmx.de> wrote: > Hello Michael, > > yes please go back and continue this, this is interesting. > > @Matt we are always happy to have new volunteers to help us maintain Ant > :-) > > Ant’s minimum Java version is 1.5 so we are good on that side. > > Regards, > > Antoine > On Mar 31, 2014, at 5:28 PM, Michael Clarke <michael.m.cla...@gmail.com> > wrote: > > > I had started this a few months back ( > > https://github.com/mc1arke/ant/tree/JUnit4Conversion) but got > side-tracked > > due to a job change. I'd be happy to go back and continue/finish the work > > if there's a general demand for it. > > > > > > On 31 March 2014 01:14, Matt Sicker <boa...@gmail.com> wrote: > > > >> I'd be a willing volunteer to help port the unit tests to JUnit 4. There > >> are various methods to using JUnit 4 with JUnit 3 test cases, suites, > etc., > >> that allow for easier migration as well. I do know that JUnit 4 has a > >> minimum requirement of Java 1.5 at least due to annotations. > >> > >> > >> On 30 March 2014 18:53, Antoine Levy Lambert <anto...@gmx.de> wrote: > >> > >>> Hello Matt, > >>> > >>> thanks for this suggestion. > >>> > >>> I have not used the JUnit TemporaryFolder rule because it is introduced > >> in > >>> JUnit 4 and the Ant test cases are extending > >>> a class of JUnit 3. > >>> > >>> The policy of the Ant project is usually to keep everything binary > >>> compatible ... > >>> > >>> If there is interest and willing volunteers and a consensus we could > >>> change that, at least in the case of BuildFileTest and JUnit 3/4 and > base > >>> "BuildFileTest" on JUnit 4. > >>> > >>> Regards, > >>> > >>> Antoine > >>> On Mar 23, 2014, at 1:50 PM, Matt Sicker <boa...@gmail.com> wrote: > >>> > >>>> Could you use the JUnit TemporaryFolder rule? That appears to be > rather > >>>> threadsafe. > >>>> > >>>> > >>>> On 23 March 2014 11:28, Antoine Levy Lambert <anto...@gmx.de> wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> Thanks to John Elion for this contribution. > >>>>> > >>>>> I have tried it on the Ant test cases. This makes the execution of > the > >>>>> test cases shorter by 3 minutes with 2 threads [ not sure what is the > >>> total > >>>>> time because I also run the antunit tests ]. > >>>>> > >>>>> Some of our test cases do not support parallelism because they are > >>>>> creating and dropping temporary directories and files which have the > >>> same > >>>>> names. > >>>>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > >>> For additional commands, e-mail: dev-h...@ant.apache.org > >>> > >>> > >> > >> > >> -- > >> Matt Sicker <boa...@gmail.com> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > > -- Matt Sicker <boa...@gmail.com>
