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

Support custom junit-platform.properties location #2195

Open
1 task
sormuras opened this issue Feb 24, 2020 · 4 comments
Open
1 task

Support custom junit-platform.properties location #2195

sormuras opened this issue Feb 24, 2020 · 4 comments

Comments

@sormuras
Copy link
Member

sormuras commented Feb 24, 2020

At the moment, the JUnit Platform properties are loaded from the first (and sole) resource named junit-platform.properties available via the ClassLoader resource-loading facility.

Internally, the JUnit Platform Launcher already supports by-passing this logic by providing an explicit location of a junit-platform.properties file or stream.

Deliverables

  • Introduce a new launcher system property, like junit.platform.properties.location, that lets users specify an alternate location of the JUnit Platform properties file to load.
@sbrannen sbrannen added this to the 5.7 M1 milestone Feb 24, 2020
@sbrannen sbrannen changed the title Support launcher's configuration of junit-platform.properties location Support custom junit-platform.properties location Mar 30, 2020
@marcphilipp marcphilipp modified the milestones: 5.7 M1, 5.7 M2 Apr 17, 2020
@marcphilipp marcphilipp modified the milestones: 5.7 M2, 5.7 Backlog Jun 5, 2020
@stale
Copy link

stale bot commented Jun 5, 2021

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.

@stale stale bot added the status: stale label Jun 5, 2021
@marcphilipp marcphilipp removed this from the 5.8 Backlog milestone Jun 19, 2021
@stale stale bot removed the status: stale label Jun 19, 2021
@stale
Copy link

stale bot commented Jun 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.

@stale stale bot added the status: stale label Jun 19, 2022
@stale
Copy link

stale bot commented Jul 11, 2022

This issue has been automatically closed due to inactivity. If you have a good use case for this feature, please feel free to reopen the issue.

@stale stale bot closed this as completed Jul 11, 2022
@mbuchner
Copy link

mbuchner commented May 8, 2024

Would love to see this feature! Especially when you use Tagging and Grouping of tests - some you want to run sequentially some can be parallelized.

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

No branches or pull requests

4 participants