Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add a system property to force the invalidation of the instant execution cache, to use to benchmark or profile writing to the instant execution cache.

Fix for previous commit.

  1. … 1 more file in changeset.
Fix for previous commit.

  1. … 1 more file in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 7 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 33 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 39 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 33 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 33 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 39 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 7 more files in changeset.
Do not write the source paths for a `CopySpec` multiple times to the instant execution cache.

Previously, these were written once when the `CopySpec` was serialized and once when the associated input property spec was serialized.

This commit adds some special case handling for this case. It also preserves the identity of each `FileTree` and `FileCollection` instance for each task to enable short circuiting when the same file collections are referenced via multiple paths, such as in the `CopySpec` case.

  1. … 39 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 2 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 2 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 1 more file in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 2 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 2 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 2 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 2 more files in changeset.
Track the source paths for a `CopySpec` in a `ConfigurableFileCollection` rather than a `Set<Object>`.

This will allow instant execution serialization to better deal with serializing these paths.

  1. … 1 more file in changeset.
Fix for previous commit.

Fix for previous commit.

Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Do not serialize multiple copies of a `CopySpec` to the instant execution cache, for a given task.

Previously, certain specs and their children would be written several times. For example, the `metaInf` spec for a `Jar` task would be written twice, which includes the manifest generation.

This not only avoids the cost of writing the same data several times but also the cost of calculating the spec contents several times, which can be expensive.

  1. … 1 more file in changeset.
Add codecs for Stack/Vector