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.

Sign up for GitHub

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

Jump to bottom

Use junit.jupiter as prefix for Jupiter configuration parameters #1004

Closed
7 tasks done
sbrannen opened this issue Aug 4, 2017 · 2 comments
Closed
7 tasks done

Use junit.jupiter as prefix for Jupiter configuration parameters #1004

sbrannen opened this issue Aug 4, 2017 · 2 comments
Assignees
@sbrannen
Labels
component: Jupiter type: task
Milestone
5.0 RC3

Comments

@sbrannen
Copy link
Member

sbrannen commented Aug 4, 2017 •
edited
Loading

Overview

JUnit Jupiter currently supports the following configuration parameters, which misleadingly seem to apply to anything related to JUnit.

  • junit.extensions.autodetection.enabled
  • junit.conditions.deactivate

Related Issues

Deliverables

  • Use junit.jupiter as a prefix for all configuration parameter names that are specific to JUnit Jupiter.
  • Update Constants.
  • Update User Guide.
  • Update release notes.

Checklist:
@sbrannen sbrannen added this to the 5.0 RC3 milestone Aug 4, 2017
@sbrannen sbrannen self-assigned this Aug 4, 2017
@sbrannen
Copy link
Member Author

sbrannen commented Aug 4, 2017

in progress

sbrannen added a commit that referenced this issue Aug 4, 2017
@sbrannen
Use junit.jupiter as prefix for Jupiter config params
c9ddcb1 
Prior to this commit, configuration parameters that were specific to
JUnit Jupiter used a prefix of "junit" instead of "junit.jupiter" which
could lead to confusion regarding scope of applicability and future
conflicts between various test engines.

This issue addresses these issues by renaming junit.conditions.deactivate
and junit.extensions.autodetection.enabled to
junit.jupiter.conditions.deactivate and
junit.jupiter.extensions.autodetection.enabled, respectively.

Issue: #1004
@sbrannen
Copy link
Member Author

sbrannen commented Aug 4, 2017

Resolved in commit c9ddcb1.

@sbrannen sbrannen closed this as completed Aug 4, 2017
@ghost ghost removed the status: in progress label Aug 4, 2017
@sbrannen sbrannen mentioned this issue Aug 4, 2017
Closed
9 tasks
Andrei94 pushed a commit to Andrei94/junit5 that referenced this issue Jun 23, 2018
@sbrannen @Andrei94
Use junit.jupiter as prefix for Jupiter config params
2bbf381 
Prior to this commit, configuration parameters that were specific to
JUnit Jupiter used a prefix of "junit" instead of "junit.jupiter" which
could lead to confusion regarding scope of applicability and future
conflicts between various test engines.

This issue addresses these issues by renaming junit.conditions.deactivate
and junit.extensions.autodetection.enabled to
junit.jupiter.conditions.deactivate and
junit.jupiter.extensions.autodetection.enabled, respectively.

Issue: junit-team#1004
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbrannen sbrannen

Labels
component: Jupiter type: task
Projects
None yet
Milestone
5.0 RC3
Development

No branches or pull requests
1 participant
@sbrannen