You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/03/29 08:03:00 UTC

[jira] [Closed] (SUREFIRE-1764) Upgrade Surefire 2.22.x to junit-platform-launcher 1.6.1

     [ https://issues.apache.org/jira/browse/SUREFIRE-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-1764.
----------------------------------

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=f14da3b893805c658b7a6fdd1ff7732e467b3603

> 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.3.4#803005)