-
Notifications
You must be signed in to change notification settings - Fork 37
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Currently, we handle JUnit 5 by only handling an explicit dependency on junit-jupiter-api:
gradle-modules-plugin/src/main/java/org/javamodularity/moduleplugin/TestEngine.java
Lines 9 to 21 in 54b55d2
| public enum TestEngine { | |
| JUNIT_4("junit", "junit", "junit", "junit"), | |
| JUNIT_5("org.junit.jupiter", "junit-jupiter-api", "org.junit.jupiter.api", "org.junit.platform.commons"), | |
| TESTNG("org.testng", "testng", "testng", "testng"); | |
| private final String groupId; | |
| private final String artifactId; | |
| public final String moduleName; | |
| public final String addOpens; | |
| TestEngine(String groupId, String artifactId, String moduleName, String addOpens) { |
However, since JUnit 5.4, a new aggregate junit-jupiter artifact is available.
We should handle this artifact in the same way as we handle junit-jupiter-api.
Issue inspired by #129.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request