[
https://issues.apache.org/jira/browse/SUREFIRE-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480545#comment-17480545
]
Tibor Digana commented on SUREFIRE-1764:
----------------------------------------
[~sjaranowski]
This issue was open for one reason. The AbstractSurefireMojo has much better
opportunities to resolve and adjust JUnit5 provider dependencies especially
org.junit.platform:junit-platform-launcher. This branch does not. And that's
the reason why this ticket was open.
Updating the version in master does not make sense because it breaks the old
users. Regarding the reflections, the surefire-junit-platform does not have
much reflections, we actually included it the first time few days ago.
> Upgrade Surefire 2.22.x to junit-platform-launcher 1.6.1
> --------------------------------------------------------
>
> Key: SUREFIRE-1764
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1764
> Project: Maven Surefire
> Issue Type: Task
> Components: JUnit 5.x support
> Affects Versions: 2.22.2
> Reporter: Christian Stein
> Assignee: Christian Stein
> Priority: Major
> Fix For: 2.22.3
>
>
> Copied from https://github.com/junit-team/junit5/issues/2028
> > In https://github.com/junit-team/junit5/issues/1909 we've improved error
> > reporting for engine discovery/execution failures. The relevant changes are
> > in DefaultLauncher which is contained in the junit-platform-launcher
> > artifact. Since most build tools and IDEs bundle that artifact we need to
> > reach out to them and ask them to update to Jupiter/Vintage 5.6 (Platform
> > 1.6).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
