Skip to content

Add support for new junit-jupiter artifact ID of JUnit 5 #130

Closed
@tlinkowski

Description

@tlinkowski

Currently, we handle JUnit 5 by only handling an explicit dependency on junit-jupiter-api:

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

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions