Skip to content

JUnit5 dependencies in poms to test scope #3

Description

@c-guntur

Code that relies on JUnit5, currently resides in the production directories at src/main/java. This causes the maven dependency to be in production scope and not test scope. Move such code to a separate module and depend on that module in the katas. The poms for the katas can then move all JUnit dependencies to test scope.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions