[FLINK-33629] Introduce ArchTest rules to ban Junit 4 for modules already completed the migration

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.18.0
• Fix Version/s: 1.19.0
• Component/s: Tests
• Labels: pull-request-available
• Assignee: jiabao.sun
• Reporter: jiabao.sun
• Created: 23/Nov/23 11:22
• Updated: 24/Nov/23 15:37
• Resolved: 24/Nov/23 15:37

Description

Currently, many modules have already completed the migration to JUnit 5, and we need to prevent the introduction of JUnit 4 tests in new PRs.

However, completely removing the dependency on JUnit 4 is challenging. It requires defining JUnit 4 as optional in the flink-parent module and allowing sub-modules to selectively include it. However, this approach still cannot solve the issue of transitive dependencies.

Therefore, considering introducing new rules in ArchTest to prohibit the usage of JUnit 4 in modules that have already completed the migration.

Issue Links

• links to: GitHub Pull Request #23790