Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Address review feedback

Rebaseline all performance test scenarios

There seems to be tiny gradual regression in performance, which causes unbearable

flakiness. Rebaselining all scenarios to catch future regressions.

  1. … 16 more files in changeset.
Rebaseline NativeCleanBuildPerformanceTest

It seems to have gradual tiny regressions. Rebaselining.

Rebaseline TaskOutputCachingSwiftPerformanceTest

TaskOutputCachingSwiftPerformanceTest seems to have a small regression

since long time ago. Rebaselining it.

Update released version to latest snapshot

Update library versions in build init to latest for 5.8

Update version to 5.8

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.

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.

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.

Publish 5.6-20190722230056+0000

Add specific serialization to the instant execution cache for the Guava immutable collection types. These are the classes used by Gradle core, not those that a plugin may happen to use (which are still yet supported).

Add specific serialization to the instant execution cache for the Guava immutable collection types. These are the classes used by Gradle core, not those that a plugin may happen to use (which are still not supported).

Add specific serialization to the instant execution cache for the Guava immutable collection types. These are the classes used by Gradle core, not those that a plugin may happen to use (which are still not supported).

Remove displayName from work queue api for now

Remove displayName from work queue api for now

Remove displayName from work queue api for now

Represent classes serialized to the instant execution cache using an integer id, rather than a string class name.

Apart from reducing the amount of stuff written to the cache, this will also allow multiple classes with the same name (but different ClassLoaders) to be referenced in the instant execution state.

Represent classes serialized to the instant execution cache using an integer id, rather than a string class name.

Apart from reducing the amount of stuff written to the cache, this will also allow multiple classes with the same name (but different ClassLoaders) to be referenced in the instant execution state.

Represent classes serialized to the instant execution cache using an integer id, rather than a string class name.

Apart from reducing the amount of stuff written to the cache, this will also allow multiple classes with the same name (but different ClassLoaders) to be referenced in the instant execution state.

Add zip bomb detection test for final artifacts

Add zip bomb detection test for final artifacts

Add zip bomb detection test for final artifacts

Add zip bomb detection test for final artifacts

Add zip bomb detection test for final artifacts

Add zip bomb detection test for final artifacts

Add zip bomb detection test for final artifacts

Add documentation

    • -0
    • +24
    /subprojects/docs/src/docs/release/notes.md
De-incubate a number of dependency management related APIs

  1. … 101 more files in changeset.
De-incubate a number of dependency management related APIs

  1. … 97 more files in changeset.