Gradle plugins classpath differs between builds running with and without '--scan'

[jjohannes]

This has the effect that many local build do not profit much from the remote build cache if they run without --scan

This issue is likely that --scan also auto-applies the com.gradle.develocity plugin and that that is happening before we apply it from inside org.hiero.gradle.build.

[jjohannes]

Confirmed. --scan is adding the plugin a second time before we add it. This alters the plugin classpath order, which invalidates caches:

• Plugin classpath with --scan: https://scans.gradle.com/s/yl6znzpnpbu7w/build-dependencies?toggled=W1swXSxbMCwwXV0
• Plugin classpath without --scan: https://scans.gradle.com/s/l6q5gtxeij2li/build-dependencies?toggled=W1swXSxbMCwwXV0

There is no way to force --scan to not do this. The only option would be to apply the com.gradle:develocity-gradle-plugin plugin directly in every settings.gradle.kts file.

Therefore, instead of using --scan we will start using a custom build parameter -Pscan and print a warning if --scan is used: #77

We change the setup to always publish on CI and not use the --scan parameter.