Gradle

Avoid reaching over project boundaries for binary compatibility check

Signed-off-by: Felipe Lima <felipe.lima@gmail.com>

Precompute message in order not to leak Project instance

Updated for build scan plugin v2.0

Introduce a hash of the component metadata rules, so that we can

cache different processed metadata based on the hash. This is a

performance optimization, which allows setting different processed

metadata on the "cached metadata" instance, based on a rules hash.

The rule hash is more stable when using class-based rules. If not,

then we have instance based rules which are opaque to Gradle, meaning

that we're going to create as many instances of processed metadata

as there are rules instantiated.

The KotlinCompile task logger goes through RMI to the Kotlin Compiler

daemon. Holding a Project instance per task exacerbated a memory leak

in the Kotlin compiler infrastructure.

Signed-off-by: Paul Merlin <paul@gradle.com>

I stumbled upon missing a bit more context about the supported version ranges in Gradle. There is also a Issue about that https://github.com/gradle/gradle/issues/5603 though this is not a fully fledged explanation it is a small improvement of the current doc. I would propose to add a additional paragraph e.g. in customizing_dependency_resolution_behavior.adoc

Signed-off-by: Niklas Grebe <niklas.grebe@innogames.com>

This will make it easier to add additional data without changing all method signatures.