Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
System properties as build logic inputs

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

  1. … 19 more files in changeset.
Fix `:instantExecution` warnings

  1. … 4 more files in changeset.
Do not write bean property names to the instant execution cache. Instead, write and read fields in a deterministic order.

  1. … 5 more files in changeset.
Do not write bean property names to the instant execution cache. Instead, write and read fields in a deterministic order.

  1. … 5 more files in changeset.
Restore eager evaluation of some functional types when writing to the instant execution cache.

  1. … 1 more file in changeset.
Restore eager evaluation of some functional types when writing to the instant execution cache.

  1. … 1 more file in changeset.
Restore eager evaluation of some functional types when writing to the instant execution cache.

  1. … 1 more file in changeset.
Restore eager evaluation of some functional types when writing to the instant execution cache.

  1. … 1 more file in changeset.
Move serialization of `Closure` instances to a separate `Codec` rather than hard-coded in bean serialization.

  1. … 2 more files in changeset.
Move serialization of `Closure` instances to a separate `Codec` rather than hard-coded in bean serialization.

  1. … 2 more files in changeset.
Move serialization of `Closure` instances to a separate `Codec` rather than hard-coded in bean serialization.

  1. … 2 more files in changeset.
Move serialization of `Closure` instances to a separate `Codec` rather than hard-coded in bean serialization.

  1. … 2 more files in changeset.
Move serialization of `Closure` instances to a separate `Codec` rather than hard-coded in bean serialization.

  1. … 2 more files in changeset.
Move serialization of `Provider` types to several `Codec` implementations, rather than hard-coded into bean serialization.

  1. … 7 more files in changeset.
Move serialization of `Provider` types to several `Codec` implementations, rather than hard-coded into bean serialization.

  1. … 7 more files in changeset.
Move serialization of `Provider` types to several `Codec` implementations, rather than hard-coded into bean serialization.

  1. … 7 more files in changeset.
Move serialization of `Provider` types to several `Codec` implementations, rather than hard-coded into bean serialization.

  1. … 7 more files in changeset.
Move serialization of `Provider` types to several `Codec` implementations, rather than hard-coded into bean serialization.

  1. … 7 more files in changeset.
Do not eagerly evaluate functional types such as `Callable` when writing to the instant execution cache. Eagerly evaluate only those types whose purpose is better understood, such as `Provider` or `FileCollection`.

  1. … 1 more file in changeset.
Do not eagerly evaluate functional types such as `Callable` when writing to the instant execution cache. Eagerly evaluate only those types whose purpose is better understood, such as `Provider` or `FileCollection`.

  1. … 1 more file in changeset.
Do not eagerly evaluate functional types such as `Callable` when writing to the instant execution cache. Eagerly evaluate only those types whose purpose is better understood, such as `Provider` or `FileCollection`.

  1. … 1 more file in changeset.
Do not eagerly evaluate functional types such as `Callable` when writing to the instant execution cache. Eagerly evaluate only those types whose purpose is better understood, such as `Provider` or `FileCollection`.

  1. … 1 more file in changeset.
Do not eagerly evaluate functional types such as `Callable` when writing to the instant execution cache. Eagerly evaluate only those types whose purpose is better understood, such as `Provider` or `FileCollection`.

  1. … 1 more file in changeset.
Serialize references to `WorkerExecutor` to the instant execution cache.

Also serialize broken `Provider<T>` instances, in the same way that broken `FileCollection` instances are serialized. This is really just a work around, and we should instead offer ways to avoid writing these broken instances to the cache.

  1. … 6 more files in changeset.
Serialize references to `WorkerExecutor` to the instant execution cache.

Also serialize broken `Provider<T>` instances, in the same way that broken `FileCollection` instances are serialized. This is really just a work around, and we should instead offer ways to avoid writing these broken instances to the cache.

  1. … 6 more files in changeset.
Change the instant execution cache bean serialization so that it honors the `writeReplace()` contract for `Serializable` types.

This allows a plugin to use the Guava collection types, which happen to use this contract for serialization. This could be viewed as a work around for the lack of support for multiple classes with the same name (and that is certainly the motivation). However, this provides a potential escape hatch for plugin authors to work around serialization issues. It also provides a nice migration path for re-using the bean serialization in other places, such as task properties, isolated work parameters and tooling models, all of which currently use Java Serialization as the general purpose contract.

  1. … 10 more files in changeset.
Change the instant execution cache bean serialization so that it honors the `writeReplace()` contract for `Serializable` types.

This allows a plugin to use the Guava collection types, which happen to use this contract for serialization. This could be viewed as a work around for the lack of support for multiple classes with the same name (and that is certainly the motivation). However, this provides a potential escape hatch for plugin authors to work around serialization issues. It also provides a nice migration path for re-using the bean serialization in other places, such as task properties, isolated work parameters and tooling models, all of which currently use Java Serialization as the general purpose contract.

  1. … 10 more files in changeset.
Change the instant execution cache bean serialization so that it honors the `writeReplace()` contract for `Serializable` types.

This allows a plugin to use the Guava collection types, which happen to use this contract for serialization. This could be viewed as a work around for the lack of support for multiple classes with the same name (and that is certainly the motivation). However, this provides a potential escape hatch for plugin authors to work around serialization issues. It also provides a nice migration path for re-using the bean serialization in other places, such as task properties, isolated work parameters and tooling models, all of which currently use Java Serialization as the general purpose contract.

  1. … 10 more files in changeset.
Do not deserialize all `List` implementations from the instant execution cache as `ArrayList`, as a step towards support for plugins using Guava types.

Also simplify the contract that codecs use to write values, making it symmetrical for writing and reading.

  1. … 7 more files in changeset.
Do not deserialize all `List` implementations from the instant execution cache as `ArrayList`, as a step towards support for plugins using Guava types.

Also simplify the contract that codecs use to write values, making it symmetrical for writing and reading.

  1. … 7 more files in changeset.