JUnit 4 has reached the end of active development and is only receiving minimal maintenance updates. Since OpenELIS now uses Java 21 and Jakarta EE (jakarta.*), staying on JUnit 4 could limit compatibility with newer testing tools and libraries.
JUnit 5 offers modern features, active support, and full Jakarta compatibility — making it a natural step forward.
Question:
Should we start thinking about gradual migration from JUnit 4 to JUnit 5 to align with current Java and Jakarta standards