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. > Den tis 20 mars 2018 16:28Stefan Bodewig <bode...@apache.org> skrev: >> I've just added a POM for ant-junitlauncher and it currently fails to >> build as >> org.apache.tools.ant.taskdefs.optional.junitlauncher.SingleTestClass has >> a dependency on org.junit.Test and I haven't declared any dependency on >> JUnit4 inside the POM (only transitively with scope test). This class is in src/main and the test works fine even if I remove the @Test annotation. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org