@rmannibucau @sormuras I will try to test @rmannibucau's test project and `scope=provided` dependency `junit-jupiter-engine` in our provider `surefire-junit-platform`. I think personally that the provider should be only compiled with a help of 3rd party dependencies but the runtime classpath should not use these dependencies because they are subject of declaring by user in POM. This fix would be easy and since every user has to use either `junit-jupiter-engine` or `junit-vintage-engine` the transitive dependency `junit-platform-launcher` appears in both. Is there any engine where the `junit-platform-launcher` does not exist?
[ Full content available at: https://github.com/apache/maven-surefire/pull/193 ] This message was relayed via gitbox.apache.org for [email protected]
