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

Auto add junit-platform-launcher to classpath #1212

Merged
merged 1 commit into from
May 18, 2023

Conversation

hcoles
Copy link
Owner

@hcoles hcoles commented May 18, 2023

The pitest minions require a version of the junit-platform-launcher which matches the version of junit 5 used by the SUT. Previously this was provided by the cludge of shading it into the junit5 plugin, but this causes constant headaches with version mismatched.

This change pulls in a matching version of platform-launcher in the same manner that surefire does. It also allows junit dependencies to be explicitly included pitest config should this resolution give the wrong results.

The pitest minions require a version of the junit-platform-launcher
which matches the version of junit 5 used by the SUT. Previously
this was provided by the cludge of shading it into the junit5 plugin,
but this causes constant headaches with version mismatched.

This change pulls in a matching version of platform-launcher in the same
manner that surefire does. It also allows junit dependencies to be
explicitly included pitest config should this resolution give the wrong
results.
@nagkumar
Copy link

Is this solution avoiding the need for asking for an explicitly pitest-junit plugin version as asked at

#1182

@hcoles
Copy link
Owner Author

hcoles commented May 19, 2023

@nagkumar This (largely) removes the need to match the plugin version to the version of junit in use.

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

Successfully merging this pull request may close these issues.

2 participants