Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove synthetic accessors for internal private symbol references

  1. … 889 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 896 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 901 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 901 more files in changeset.
Do not run the constructors of tasks that are deserialized from the instant execution cache.

  1. … 21 more files in changeset.
Do not run the constructors of tasks that are deserialized from the instant execution cache.

  1. … 21 more files in changeset.
Do not run the constructors of tasks that are deserialized from the instant execution cache.

  1. … 21 more files in changeset.
Do not run the constructors of tasks that are deserialized from the instant execution cache.

  1. … 20 more files in changeset.
Use 'implementation' dependencies everywhere

    • -1
    • +1
    ./org/gradle/util/ConfigureUtilTest.groovy
  1. … 281 more files in changeset.
Use 'implementation' dependencies everywhere

    • -1
    • +1
    ./org/gradle/util/ConfigureUtilTest.groovy
  1. … 278 more files in changeset.
Use 'implementation' dependencies everywhere

    • -1
    • +1
    ./org/gradle/util/ConfigureUtilTest.groovy
  1. … 281 more files in changeset.
Use 'implementation' dependencies everywhere

    • -1
    • +1
    ./org/gradle/util/ConfigureUtilTest.groovy
  1. … 279 more files in changeset.
Use 'implementation' dependencies everywhere

    • -1
    • +1
    ./org/gradle/util/ConfigureUtilTest.groovy
  1. … 280 more files in changeset.
Use 'implementation' dependencies everywhere

    • -1
    • +1
    ./org/gradle/util/ConfigureUtilTest.groovy
  1. … 280 more files in changeset.
Generate read-only user type properties

  1. … 2 more files in changeset.
Generate read-only user type properties

  1. … 3 more files in changeset.
Generate read-only user type properties

  1. … 3 more files in changeset.
Generate read-only user type properties

  1. … 3 more files in changeset.
Generate read-only user type properties

  1. … 5 more files in changeset.
Generate read-only user type properties

  1. … 3 more files in changeset.
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.

  1. … 9 more files in changeset.
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.

  1. … 8 more files in changeset.
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.

  1. … 9 more files in changeset.
Do not cache type annotation metadata across builds

We only use it in DefaultTypeMetadataStore that is already cached across builds (and even that might not be worth it).

  1. … 8 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.