You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Fedotov (JIRA)" <ji...@apache.org> on 2019/01/16 12:58:00 UTC
[jira] [Commented] (IGNITE-10180) Investigate migration from Junit
4 to 5
[ https://issues.apache.org/jira/browse/IGNITE-10180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744005#comment-16744005 ]
Ivan Fedotov commented on IGNITE-10180:
---------------------------------------
[~oignatenko], I investigated the migration process to JUnit 5 and got the next results.
1. JUnit 5 was integrated to SureFire by collaboration maven and JUnit teams and some architecture aspects were suggested by JUnit developers [1]
2. Integration was provided in several steps and was finished in 2018 [2]
3. JUnit 5 framework is divided into 3 sub-projects: Jupiter - new annotations and extensions, Vintage - for running 3 and 4 JUnit versions and Platform which is used for launching new framework on JVM. So, for usage 5 version it could be necessary to add several dependencies [3].
4. Maven uses Java 6 language level. For JUnit 4 it is necessary Java 5, for JUnit 5 at least Java 8.
So, it seems that segregation into different modules was proposed by implementation issue. Moreover, apparent adjunction inconvenience JUnit4 to maven could be because of maven language level.
Anyway, nothing prevents in JUnit5 run JUnit 3 and JUnit 4 based tests on the platform with Vintage sub-project.
[1] https://github.com/apache/maven-surefire/pull/184
[2] https://issues.apache.org/jira/browse/SUREFIRE-1330
[3] https://junit.org/junit5/docs/current/user-guide/#overview-what-is-junit-5
> Investigate migration from Junit 4 to 5
> ---------------------------------------
>
> Key: IGNITE-10180
> URL: https://issues.apache.org/jira/browse/IGNITE-10180
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Oleg Ignatenko
> Assignee: Ivan Fedotov
> Priority: Major
>
> If needed, refer parent task for more details.
> Find out if Junit 5 is mature enough - specifically why maven and, especially surefire plugin, still uses Junit 4 as more comfortable from a side of adding dependencies, are there serious reasons for that or not. If it looks okay, create a new JIRA task to migrate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)