This message was deleted.

Just a random thought: if adding --scan doesn't change the classpath is because you already have the gradle-enterprise plugin in your classpath

It's the weirdest thing. Adding

--scan

always changes the classpath

It's very weird

Can I get more info about the classpath than just a hash?

For a task I guess you could print the files in a doFirst (but I don't know if there is a better way)

This classpath is not an input property or anything like that though. It's the buildscript classpath

🤔 you said its "compileKotlin" task, so it's a task, but yes, a task to compile the buildScript..

I think it's the "classpath of the task itself" vs the "compile classpath that the compiler will use", if that even makes sense?

The only thing that happens before that could be the settings.gradle

And

plugins {}

block too, right?

The other option would be writing a reproducer and the maybe you can get some help

Yep, makes sense. I'll try to see how to isolate this 👍