ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gintautas Grigelionis <>
Subject Re: Ant support for users who use JUnit5
Date Thu, 14 Dec 2017 12:22:40 GMT
FWIW, I'm for a separate task. It may simplify dropping tasks that become
mired in legacy (who needs Jasper from Tomcat 4 nowadays?)
Or maybe we should start an ant-legacy antlib? :-)


2017-12-14 12:44 GMT+01:00 Stefan Bodewig <>:

> On 2017-12-14, Jaikiran Pai wrote:
> > With that context, I would like to explain what I have attempted so
> > far and I would like inputs on whether I should follow this path
> > and/or if there are other suggestions on how we should go ahead. As
> > you are probably aware, the JUnitTask (the Ant task backing the
> > <junit> element) has very complex logic which deals with launching the
> > test runners responsible for running JUnit tests (3.x or 4.x). IMO,
> > most this logic can now be handed off to the JUnit 5 platform
> > launcher, using their APIs.
> In addition some of the complexity inside of JUnitTask stems from the
> fact that it must not refer to any JUnit 4.x API in order to be usable
> in a pure JUnit 3.x environment. If you try to add JUnit 5 on top of
> that this sounds diffciult.
> I too had toyed with the idea of adding JUnit5 support but it is quite a
> bit further down my TODO list and I've not looked into JUnit5 as deeply
> as you did. What you've got so far looks promising, please please push
> ahead.
> My idea was to create a completely new task and mainly try to keep the
> XML output the way it has been for some fifteen years so junitreport
> would still work. I even though about placing it in a separate antlib
> rather than Ant's core to allow it get released independently.
> My vote would go to a separate task.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message