Tibor17 commented on issue #850: URL: https://github.com/apache/maven-surefire/issues/850#issuecomment-3677927886
> dependencies management from surefire project should not have impact on resolved version in used project. > > As workaround you can also add to plugin dependncies: > > <dependency> > <groupId>org.junit.platform</groupId> > <artifactId>junit-platform-engine</artifactId> > <version>older.version</version> > </dependency> I created the dependency resolution mechanism in `AbstractSurefireMojo`. It was working file in 2021. These problems are in [Gradle](https://discuss.gradle.org/t/why-do-gradle-docs-specify-junit-platform-launcher-for-junit-5-tests/46286) and [IntelliJ IDEA](https://stackoverflow.com/questions/66315013/failed-to-resolve-junit-platform-launcher-1-6-3-intellij) but these bugs are dated in the year 2021 and 2023. It does not make sense to see the problem in Parent POM version because the plugin runtine simply does not care about it. It does not make sense to add `junit-platform-engine` because the mechanism in the plugin already does this job and I did it for the comfort of the user. So it is important so make Git bisec between 3.5.2 and 3.5.3. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
