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

Adjust PIT Gradle plugin configuration #2903

Merged
merged 1 commit into from Mar 27, 2022
Merged

Conversation

szpak
Copy link
Contributor

@szpak szpak commented Mar 26, 2022

Starting with PIT 1.6.7 it is just enough to have kotest-extensions-pitest on (test) classpath

Over more that parameter is already deprecated and "marked for deletion". See:
hcoles/pitest#900
szpak/gradle-pitest-plugin#277

Starting with PIT 1.6.7 it is just enough to have kotest-extensions-pitest on (test) classpath

Over more that parameter is already deprecated and "marked for deletion". See:
hcoles/pitest#900
szpak/gradle-pitest-plugin#277
@sksamuel
Copy link
Member

Did something change in PIT to automatically register Kotest? I looked at the changelog but couldn't find anything.

@szpak
Copy link
Contributor Author

szpak commented Mar 27, 2022

Please see the first linked issue:

As a result of this change the 'testPlugin' parameter is now redundant, but has been retained for this release.

@sksamuel
Copy link
Member

Ok so it must be looking for instances of org.pitest.testapi.TestPluginFactory on the classpath.

@sksamuel sksamuel merged commit 3082dc9 into kotest:master Mar 27, 2022
@szpak szpak deleted the patch-1 branch March 27, 2022 19:21
@szpak
Copy link
Contributor Author

szpak commented Mar 27, 2022

I guess so. Thanks to that you can also have multiple plugins enabled at the same time.

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.

None yet

2 participants