TaskPropertyTestUtils.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use a Supplier instead of a Factory to avoid null check

  1. … 8 more files in changeset.
Use a Supplier instead of a Factory to avoid null check

  1. … 8 more files in changeset.
Use public services in native plugins to construct `FileCollection` instances, rather than using internal `FileOperations`.

  1. … 32 more files in changeset.
Use public services in native plugins to construct `FileCollection` instances, rather than using internal `FileOperations`.

  1. … 32 more files in changeset.
Move some more direct usages of `DefaultConfigurableFileCollection` instances to instead delegate to `FileCollectionFactory`.

  1. … 12 more files in changeset.
Move some more direct usages of `DefaultConfigurableFileCollection` instances to instead delegate to `FileCollectionFactory`.

  1. … 12 more files in changeset.
Some polishing

  1. … 24 more files in changeset.
Don't use propertySpecFactory for input files

  1. … 51 more files in changeset.
Fix ignored tests, take 2

  1. … 2 more files in changeset.
Revert "Fix ignored tests"

  1. … 2 more files in changeset.
Fix ignored tests

  1. … 2 more files in changeset.
Re-use `TaskDependencyResolveContext` during task graph building (#3807)

All dependency resolution in Gradle should happen via TaskDependencyResolveContext during when building the task graph. Calling `DefaultTaskDependency.getDependencies(task)` should be avoided since it creates a new `TaskDependencyResolveContext` and needs to calculate the dependencies again.

`SkipTaskWithNoActionsExecuter` now re-uses the `TaskExecutionGraph` to determine the dependencies of a task instead of re-evaluating them.

After this commit, the task properties are resolved at three places:

- When building the task graph for walking the input files

- When checking if there a task can be executed in parallel with the currently running tasks based on on the declared outputs, destroyables and task local state

- For using the task properties during task execution

The last two places could still be unified into one, but that seems to be a little bit more complicated.

  1. … 23 more files in changeset.
Don't use now deprecated getProperties() method

Signed-off-by: Lóránt Pintér <lorant@gradle.com>

    • -0
    • +36
    ./TaskPropertyTestUtils.groovy
  1. … 6 more files in changeset.