On Fri, 22 Jun 2018 at 09:45, Stefan Bodewig <bode...@apache.org> wrote:
> On 2018-06-22, Gintautas Grigelionis wrote: > > > Well, setup-for-junit-tests states that JUnit is not available and > > quits. > > So it lacks a dependency on resolve. > > > I'd like to understand why setup targets are there at all. > > They predate resolve by far. The initial build system for Antlibs didnt > use Ivy at all but expected manual configuration and the setup targets > ensured everything was there. When Ivy was added later (by Jan?) he > probably missed to adapt a few places - like setup-for-junit-tests. > Actually, the targets are written in a way that checks explicitly for JUnit 3. Should they be rewritten to check for JUnit 4, the baseline has to be moved to all the way Ant 1.9.5 because of BuildFileRule being first available in that version. Then, the order of compile-tests target dependencies must be changed so that setup-for-junit-tests comes after antlib (which does resolve, therefore explicit resolve becomes redundant) and uses classpaths defined by resolve to check for JUnit. Gintas
