Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Replace LinkedLists with ArrayLists where possible

  1. … 71 more files in changeset.
Use plugins DSL in Javadoc code snippets

    • -1
    • +3
    ./org/gradle/language/c/CSourceSet.java
  1. … 42 more files in changeset.
Use plugins DSL in Javadoc code snippets

    • -1
    • +3
    ./org/gradle/language/c/CSourceSet.java
  1. … 42 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 42 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 42 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 36 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 42 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 36 more files in changeset.
Fix GenerateSwiftPackageManagerManifest using getProject() at execution time

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

Fix GenerateSwiftPackageManagerManifest using getProject() at execution time

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

Fix GenerateSwiftPackageManagerManifest using getProject() at execution time

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

Fix GenerateSwiftPackageManagerManifest using getProject() at execution time

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

Only query compiler version when necessary properties are set

Only query compiler version when necessary properties are set

Fix for previous commit.

  1. … 10 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 23 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 31 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 30 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 31 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 20 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 20 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

  1. … 81 more files in changeset.