[
https://issues.apache.org/jira/browse/IMPALA-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076345#comment-18076345
]
Stamatis Zampetakis commented on IMPALA-14925:
----------------------------------------------
Initially, I thought that the whole migration can be completed with a few hours
of work but it turned out a bit more complex than expected. Not sure if I will
be able to find time to bring this to completion but in order not to lose the
effort done so far I plan to share shortly some findings and progress from my
first attempt.
> Migrate from JUnit4 to JUnit6
> -----------------------------
>
> Key: IMPALA-14925
> URL: https://issues.apache.org/jira/browse/IMPALA-14925
> Project: IMPALA
> Issue Type: Task
> Components: Test
> Reporter: Stamatis Zampetakis
> Priority: Major
>
> The JUnit4 release line is in maintenance mode with the last release
> ([4.13.2|https://github.com/junit-team/junit4/releases/tag/r4.13.2]) dating
> back in Feb 13, 2021. This task is about migrating to the latest actively
> maintained release line that at this point in time is
> [6.0.3|https://github.com/junit-team/junit-framework/releases/tag/r6.0.3].
> Although it is feasible to use JUnit4 and JUnit6 at the same time through the
> vintage test engine in practice various issues arise when used in conjunction
> with some plugins such as [Maven Surefire
> Plugin|https://maven.apache.org/surefire/maven-surefire-plugin/].
> Given that the number of Java based tests are not using many exotic features,
> opting for a full migration of JUnit4 to JUnit6, i.e., dropping entirely the
> JUnit4 dependencies, is more advantageous and would simplify future
> maintenance.
> The migration guide can be found here:
> https://docs.junit.org/6.0.3/migrating-from-junit4.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
