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

Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/10/28 08:24:00 UTC

[jira] [Updated] (HDDS-9492) Ban import of JUnit4 classes in modules already migrated to JUnit5

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

ASF GitHub Bot updated HDDS-9492:
---------------------------------
    Labels: pull-request-available  (was: )

> Ban import of JUnit4 classes in modules already migrated to JUnit5
> ------------------------------------------------------------------
>
>                 Key: HDDS-9492
>                 URL: https://issues.apache.org/jira/browse/HDDS-9492
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: build, test
>            Reporter: Attila Doroszlai
>            Assignee: Attila Doroszlai
>            Priority: Major
>              Labels: pull-request-available
>
> Some modules had been completely migrated to JUnit5.  Ideally we should remove JUnit4 dependency, but it is also coming transitively from test utils.  Until the dependency can be completely removed, we should ban import of JUnit4 classes in such modules to avoid JUnit4 tests creeping back.
> The goal of this task is to introduce the ban in modules that are currently completely on JUnit5.  Test migration tasks should then also add the rule to modules being cleaned up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org