The JUnit 6.0 release introduces a unified versioning approach:
all modules of JUnit Platform, Jupiter, and Vintage now use the same version number: 6.0.0.
source - JUnit 6.x upgrade guide
As ArchUnit’s archunit-junit5 module is built against JUnit 5.x and Platform 1.x, it cannot be used in environments which adopt JUnit 6.x (Platform 6.x + Jupiter 6.x). This creates a blocker for testing strategies in modern Java projects.
Request
- Introduce a module (e.g., archunit-junit6) targeting JUnit 6.x compatibility.
- Alternatively upgrade archunit-junit5 to detect/enable JUnit 6 support when Platform 6.x and Jupiter 6.x are on the classpath.
- Handle any JUnit 6 API changes (e.g., removed modules, null‐safety annotations) as noted in the JUnit upgrade guide.
Goal
Allow teams using ArchUnit for architectural tests to migrate to JUnit 6.x without compromising dependency alignment or test stability.
The JUnit 6.0 release introduces a unified versioning approach:
source - JUnit 6.x upgrade guide
As ArchUnit’s
archunit-junit5module is built against JUnit 5.x and Platform 1.x, it cannot be used in environments which adopt JUnit 6.x (Platform 6.x + Jupiter 6.x). This creates a blocker for testing strategies in modern Java projects.Request
Goal
Allow teams using ArchUnit for architectural tests to migrate to JUnit 6.x without compromising dependency alignment or test stability.