[
https://issues.apache.org/jira/browse/SUREFIRE-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068564#comment-17068564
]
Christian Stein commented on SUREFIRE-1764:
-------------------------------------------
Commit
[https://github.com/apache/maven-surefire/commit/f14da3b893805c658b7a6fdd1ff7732e467b3603]
solves this issue for 2.22.x
Parts of it should be copied over to 3.x – or like Tibor said:
{quote}IMO The 3.0.0-M5 should fix
[SUREFIRE-1750|https://issues.apache.org/jira/browse/SUREFIRE-1750] in master
asap and then we will avoid these situations from happening again. Then the IT
should be extended with {{5.6.1}} in master and no need to add the
{{junit-platform-launcher}} dependency in the tests because the plugin will do
the same with adapting the versions (we are doing in 2.22.3 right now).
{quote}
> 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
>
> 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.3.4#803005)