2018-03-20 16:43 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2018-03-20, Gintautas Grigelionis wrote: > > > My understanding is that junitlauncher has a dependency on JUnit 4 > through > > vintage engine. I guess pom should provide profiles for engine choice. > See > > my earlier questions re the task classpath. > > Only when running the tests. The launcher task itself doesn't depend on > any of the engines at compile time. >
At least in pom there is a clear distinction between compile and runtime. I wish there was Ivy 2.5 out there so that we could have a unified ivy.xml; until then -- sorry for thinking as an end user in terms of dependencies. Gintas
