This message was deleted.

So found this issue: https://github.com/gradle/gradle/issues/8161

classpath issues, right? I think that, if the project applies the GE plugin, then this issue goes away

yeah, if settings contains GE plugin applied - I don't see such problem

This is expected. Adding

--scan

adds the Gradle Enterprise plugin to the buildscript classpath. A change to the buildscript classpath changes the implementation of all tasks.

interestingly java compile tasks stay

FROM-CACHE

The java compile tasks are part of Gradle plugin and use a different classloader which is not affected here.