Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JUnit5 dependencies in poms to test scope #3

Open
c-guntur opened this issue Jul 10, 2019 · 0 comments
Open

JUnit5 dependencies in poms to test scope #3

c-guntur opened this issue Jul 10, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@c-guntur
Copy link
Owner

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.

@c-guntur c-guntur added the enhancement New feature or request label Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant