tasks

Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

Removing a task dependency from a task instance is no longer supported (#10289)

A work node receives a context that exposes the build scoped services, rather than an empty registry, when the node is not associated with a project. This means that a node implementation does not have to carry build scoped services around in case it does not end up have an owning project, and can just locate the execution services it needs via its context when it runs.

Add missing @Override to all modules

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

Simplify how task input dependencies are discovered by `TaskInput`, so that the dependencies are visited instead of being added as artificial elements of the input file collection.

Also simplify the resolution of task dependencies provided by `TaskDependencyContainer` and `Provider` instances.

Fix task dependency inference when a mapped task output file `Property` is used as input to an `@Input` on another task.

Move some test utility methods out of the artifact transform tests into a more general place, and reuse in some of the task dependency inference tests.

Pass around empty service registry

instead of `null`.

Pass fingerprinter registry into transformer (invoker)

Allow a `WorkNodeAction` to declare which project it will require access to when it runs, if any. Use this to ensure that the project lock is held when resolving the dependency graph prior to running artifact transforms that take artifact dependencies as input.

Simplify the injection of artifact transform build dependencies factory into the `ConsumerProvidedVariant` so that it is consistent with the injection of the artifact transform dependencies themselves.

Extract a common implementation of `TaskDependencyResolveContext` that is shared in a couple of places.

Change various buildable dependency resolution types to extend `TaskDependencyContainer` rather than providing their own contract for visiting their dependencies.

This removes the need for adapters when visiting the build dependencies of dependency resolution types as part of visiting the dependencies of a task.

Change the contract through which a task finalization action is declared when visiting build dependencies, so that it is similar to how other dependencies are visited.

This change moves some complexity out of the dependency resolution artifact types and into the task dependency infrastructure, which is a better home for it and where it can be simplified.

Merge remote-tracking branch 'origin/release'

Rename Transform -> Transformation

Rework task dependency inference so that `Provider` implementations use the same `TaskDependencyContainer` interface that most other things use to declare their producer task to the task resolution infrastructure, rather than having special knowledge sprinkled around various places.

Cleaned up a bunch of `Provider` and `Property` implementations so that more logic is reused rather than reimplemented.

Fix deprecation messages in tests

Support propagation of the producer task for provider instances that are created using `Provider.map()`.

Now, when a provider represents a task or task output, whether mapped or not, that task is taken as the producer of the value and the mapping function is not called. Otherwise, the value of the provider is unpacked and resolved, as it previously was.

Rework the protocol by which providers communicate their build dependencies to consumers.