You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2024/06/26 20:58:00 UTC
[jira] [Commented] (SUREFIRE-2237) Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
[ https://issues.apache.org/jira/browse/SUREFIRE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860254#comment-17860254 ]
Michael Osipov commented on SUREFIRE-2237:
------------------------------------------
Feel free to provide a PR which has no failures...
> Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
> ------------------------------------------------------------
>
> Key: SUREFIRE-2237
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2237
> Project: Maven Surefire
> Issue Type: Dependency upgrade
> Reporter: Darius Cooper
> Priority: Minor
>
> junit-jupiter 5.10.x introduced some new classes
> Now that [spring-boot-starter-test pulls in that version|https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-test/3.2.2], tests give an error when we upgrade to the latest Spring. It would make things easier if surefire used the latest versions.
> (Cloned SUREFIRE-2157, because that was a very similar change)
> I did [notice this|https://github.com/apache/maven-surefire/blob/2fed802397f8c7de4cfc72f49ab4565e72f7aab7/pom.xml] *warning comment* in the parent pom:
> {code:java}
> <dependency>
> <!-- Do not upgrade, leads to test failures, needs analysis -->
> <groupId>org.junit</groupId>
> <artifactId>junit-bom</artifactId>
> <version>5.9.3</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)