Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix inconsistent serialization state when resolution cache expires

Resolution results are cached, but the cache may expire or entries

in the cache may be evicted, in case there are many configurations

resolved. This has the consequence that the streaming resolution

builder root factory may be called multiple times for the same

configuration, and therefore the file may be read several times

within a build.

This commit fixes a bug with attribute serialization where the state

of the serializer would make the 2d read incorrect.

Fix inconsistent serialization state when resolution cache expires

Resolution results are cached, but the cache may expire or entries

in the cache may be evicted, in case there are many configurations

resolved. This has the consequence that the streaming resolution

builder root factory may be called multiple times for the same

configuration, and therefore the file may be read several times

within a build.

This commit fixes a bug with attribute serialization where the state

of the serializer would make the 2d read incorrect.

Fix LARGE_JAVA_MULTI_PROJECT_NO_BUILD_SRC

Signed-off-by: Bo Zhang <bo@gradle.com>

Fix LARGE_JAVA_MULTI_PROJECT_NO_BUILD_SRC

Signed-off-by: Bo Zhang <bo@gradle.com>

Fix LARGE_JAVA_MULTI_PROJECT_NO_BUILD_SRC

Signed-off-by: Bo Zhang <bo@gradle.com>

Serialize values of type `Character` and `char` and `ToolingModelBuilderRegistry` when serializing to the instant execution cache.

Also warn about and discard values of type `TaskContainer` (same as `Project`, `Task`, etc).

Serialize values of type `Character` and `char` and `ToolingModelBuilderRegistry` when serializing to the instant execution cache.

Also warn about and discard values of type `TaskContainer` (same as `Project`, `Task`, etc).

Serialize values of type `Character` and `char` and `ToolingModelBuilderRegistry` when serializing to the instant execution cache.

Also warn about and discard values of type `TaskContainer` (same as `Project`, `Task`, etc).

Handle kotlin lazy properties of type `Provider<T>` when serializing to the instant execution cache.

Handle kotlin lazy properties of type `Provider<T>` when serializing to the instant execution cache.

Handle kotlin lazy properties of type `Provider<T>` when serializing to the instant execution cache.

Update released version to latest snapshot

Clean release notes and welcome message for 5.7

    • -43
    • +0
    /subprojects/docs/src/docs/release/notes.md
Clean accepted API changes

Update version to 5.7

Merge remote-tracking branch 'origin/master-test' into release-test

Update release notes to mention abstract service injection methods, managed properties and the new user manual chapter.

Also some release notes editing.

    • -10
    • +34
    /subprojects/docs/src/docs/release/notes.md
Update release notes to mention abstract service injection methods, managed properties and the new user manual chapter.

Also some release notes editing.

    • -10
    • +34
    /subprojects/docs/src/docs/release/notes.md
Publish 5.5-20190605010753+0000

Minor user manual edit.

Minor user manual edit.

Unignore and refine instant execution Groovy plugin integration test

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

Add instant execution codec for ConfigurableFileCollection

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

Add another project to the minimum runtime classpath for workers

Use OS dependent absolute path normalization in DefaultFileSystemSnapshotter

Use OS dependent absolute path normalization in DefaultFileSystemSnapshotter

Merge remote-tracking branch 'origin/lorinc/release-to-master'

Change DefaultBuildOutputCleanupRegistry path resolution to be File based

Instead of String based, to make sure the OS case sensitivity is applied to it

Add test for worker-based task completing without reacquiring project lock

This test demonstrates the current behaviour, where a worker-based task is

not considered 'complete' until it has reacquired the project lock. This will

be fixed in subsequent commits.

Add test for worker-based task completing without reacquiring project lock

This test demonstrates the current behaviour, where a worker-based task is

not considered 'complete' until it has reacquired the project lock. This will

be fixed in subsequent commits.