Is there any way to diagnose the classpath of a task that was re-executed due to changes in same? Debug output did not help, it still only prints the following lines:

Task 'projecttaskA' is not up-to-date because:

Class path of task 'projecttaskA' has changed from 2f95... to 53be....

This would help me find out why

taskA

is re-exectued each time a plugin is updated that should have no effect on that task's classpath. The task is defined in a

build-logic

included build that does not reference the changing plugin.