Closed J-Curragh closed 2 years ago
Thanks for your report. GPP is not tested with project-report and I see the aforementioned error for the first time. GPP dynamically set a version of PIT, but maybe it can be done in some other way to avoid that problem. Unfortunately, I don't have any immediate workaround for you (other than not using project-report :-/).
Update. Probably with lower Gradle version it would be just a warning. Or maybe there is even a switch to convince Gradle 7.3 to - temporary - wink at it.
Alright. Thank you @szpak, I will try that out on Tuesday and let you know.
Downgrading Gradle (<6.8) seems to have done the trick.
Glad to hear and thanks for getting back with the update. I would keep it open - Gradle 7.x is in general supported (there are even some basic functional tests for that), so that corner case - with project-report - has to be investigated.
The fix provided in #313 will be included in the next release.
I am using Gradle's project-report plugin to generate reports detailing project dependencies and properties.
I get the following error message when running the
projectReport
gradle task.This is an excerpt from the build.gradle file
Gradle is throwing an error - see here.
Perhaps this is because pitest is adding a dependency to pitest-command-line after it has already been resolved in gradle?
Full stack trace: