-
Notifications
You must be signed in to change notification settings - Fork 26
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
Plugin crashes when junit-jupiter-engine
dependency is not explicitly declared
#105
Comments
Stephan202
added a commit
to PicnicSupermarket/error-prone-support
that referenced
this issue
Jan 14, 2024
This largely reverts commit dff67fe, avoiding the issue described in pitest/pitest-junit5-plugin#105.
rickie
pushed a commit
to PicnicSupermarket/error-prone-support
that referenced
this issue
Jan 14, 2024
This largely reverts commit dff67fe, avoiding the issue described in pitest/pitest-junit5-plugin#105.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After merging PicnicSupermarket/error-prone-support#973, in which explicit test dependencies on
junit-jupiter-engine
were dropped (since Surefire anyway provides the test framework implementation based on an analysis of the test classpath), we noticed that Pitest started failing. See PicnicSupermarket/error-prone-support#972 for an example. Reported output:In our case the cause was not so hard to determine, but it could be a real head-scratcher if this issue happens when a user introduces Pitest for the first time. So the question is: can the plugin be updated to mirror whatever Surefire does?
The text was updated successfully, but these errors were encountered: