Carsten Otto

``` Task ':application:pitest' is not up-to-date because: Value of input property 'additionalClasspathFilePath' has changed for task ':application:pitest' Value of input property 'defaultFileForHistoryDataPath' has changed for task ':application:pitest' ```

I don't know a whole lot about gradle plugins, but it seems these two methods/properties are not in use? I managed to get things working by simply removing them.

In my understanding you want to log a helpful message to tell the user about a configuration issue (missing `dependsOn`?). If this is correct, I suggest to just drop this...

This is creating lots of output when running gradle in continuous mode, to the point that I had to disable the plugin.

We won't be able to use CPD once we switched to Gradle, but that won't happen for a few weeks or so. Besides, we can live without CPD, although it's...

https://github.com/C-Otto/cpdtestfixtures If CPD is configured before the integration tests are introduced, for reasons I don't understand CPD also scans the integration test sources: https://github.com/C-Otto/cpdtestfixtures/commit/fbf644bc9fd9f90e8f2f0e6a1f73557f2cd3b582 If you enable the java-test-fixtures plugin...

It looks like your IT adds a file with duplications to `src/main/java`? That doesn't look right to me. Anyway, for me the hotfix/hack using `evaluationDependsOnChildren()` also helped here (see linked...

Thanks for the snippets, I'll try them out tomorrow. I agree, a bit more documentation wouldn't hurt, especially related to the warning I posted earlier (I've seen it several times...

I'm unable to create a configuration that combines the scan for all subprojects, as described in your response above. I'm using this snippet for all variants described below: ``` evaluationDependsOnChildren()...

Sorry, I'm confused about the current state. Let's ignore the "global scan", i.e. using CPD to find duplicates between subprojects. My understanding: This is a bug in your code, where...