2018-05-04 8:32 GMT+02:00 Jan Matèrne (jhm) <apa...@materne.de>:

> Changing Ants own test to use JUnit5 does not mean we have to change Ant
> itself and don't have to cut a release.
>
> What do you want to move to "ant-legacy"?
>

You're right, JUnit 5 puts no new requirements on Ant.

Should we continue a "legacy" discussion, that would at least include
anything related to J2EE and VCS + deprecated tasks and listeners.

Gintas

Reply via email to