From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

The javadocs for `ResolvableDependencies#getResolutionResult` say: "This will resolve the dependency graph but will not resolve or download the files."

however, in order to get a configuration cache compatible input, I _cannot_ use a `Configuration` as an input, it triggers serialization errors

so I have to use `config.getIncoming().getResolutionResult()`, but this, if the javadocs are correct, will trigger resolution too early

the example at <https://github.com/adammurdoch/dependency-graph-as-task-inputs/blob/main/plugins/src/main/java/ReportDependencyGraphTask.java#L20> also uses a `ResolvedComponentResult` as an input, which assumes that the resolution has happened already.

(it seems, however, that I can use `ResolvableDependencies` as a config cache, lazy-compatible input)

`config.incoming.resolutionResult.rootComponent` is the lazy provider one that is intended to be wired to task inputs and such

so the javadocs are confusing, because they imply that `config.incoming.resolutionResult` triggers resolution

This is indeed wrong. calling `config.incoming.resolutionResult` doesn´t trigger resolution, `config.incoming.resolutionResult.root` or other functions on `ResolutionResult` do, except for `config.incoming.resolutionResult.rootComponent`

Can you point to the confusing part of javadoc?

Heh :slightly_smiling_face: I can promise to do what I can to get your system property provider one merged eventually once I figure out the perf problem :wink:

<https://github.com/gradle/gradle/issues/24326>