Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix fixtures for Windows

The test fixtures do not normalize line endings, which causes

unexpected build failures under Windows.

There's also a date format used for timestamps which may

return a different value under Windows depending on the

current timezone and locale.

Polish

    • -1
    • +3
    /.teamcity/Gradle_Check/model/BucketProvider.kt
    • -3
    • +3
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Polish

    • -1
    • +3
    /.teamcity/Gradle_Check/model/BucketProvider.kt
    • -3
    • +3
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Simplify JSoup transforms

Publish 6.0.1-20191202045933+0000

Combine and rewrite all documentation generation

  1. … 262 more files in changeset.
Update released version to latest snapshot

Update library versions in build init to latest for 6.2

Clean release notes and welcome message for 6.2

    • -39
    • +11
    /subprojects/docs/src/docs/release/notes.md
Update version to 6.2

Clean accepted API changes

Attempt to reproduce

Dedupe shared identity handling

Polish `DefaultInstantExecution`

- Better variable names

Polish `TransformationNodeReferenceCodec`

- Replace `if null` by elvis expression

Publish 6.0.1-20191202000048+0000

Rename `BuildEventsListenerRegistry.subscribe()` to `onTaskCompletion()` to make the current contract more explicit.

At some point, we may may allow plugins to receive finish events from additional operation types, in which case new methods can be added and this method left as a convenience or deprecated.

Also add an internal `onBuildOperationComplete()` method, which gradle-profiler can use to subscribe to build operations in an instant execution friendly way. The tooling API event stream doesn't carry quite enough information for gradle-profiler at the moment. So add this method instead of keeping the work-arounds in instant execution and complexity in gradle-profiler. We may replace this method with a public one once the tooling API event stream carries the required information.

Rename `BuildEventsListenerRegistry.subscribe()` to `onTaskCompletion()` to make the current contract more explicit.

At some point, we may may allow plugins to receive finish events from additional operation types, in which case new methods can be added and this method left as a convenience or deprecated.

Also add an internal `onBuildOperationComplete()` method, which gradle-profiler can use to subscribe to build operations in an instant execution friendly way. The tooling API event stream doesn't carry quite enough information for gradle-profiler at the moment. So add this method instead of keeping the work-arounds in instant execution and complexity in gradle-profiler. We may replace this method with a public one once the tooling API event stream carries the required information.

Rename `BuildEventsListenerRegistry.subscribe()` to `onTaskCompletion()` to make the current contract more explicit.

At some point, we may may allow plugins to receive finish events from additional operation types, in which case new methods can be added and this method left as a convenience or deprecated.

Also add an internal `onBuildOperationComplete()` method, which gradle-profiler can use to subscribe to build operations in an instant execution friendly way. The tooling API event stream doesn't carry quite enough information for gradle-profiler at the moment. So add this method instead of keeping the work-arounds in instant execution and complexity in gradle-profiler. We may replace this method with a public one once the tooling API event stream carries the required information.

Bump layout format

Bump layout format

Bump layout format

Bump layout format

Unit test coverage for previous commit.

Optimize how to locate metadata file in cache

This commit avoids the use of `search` on the file store

which is quite expensive (18% regression on exclude rule

merging perf test).

Instead we add a method on the filestore to give us the

path to the file given its coordinates.

Optimize how to locate metadata file in cache

This commit avoids the use of `search` on the file store

which is quite expensive (18% regression on exclude rule

merging perf test).

Instead we add a method on the filestore to give us the

path to the file given its coordinates.

Optimize how to locate metadata file in cache

This commit avoids the use of `search` on the file store

which is quite expensive (18% regression on exclude rule

merging perf test).

Instead we add a method on the filestore to give us the

path to the file given its coordinates.

Use file names instea of Ivy artifact names for comparison

This commit reworks the generation of verification file and

verification itself in order to use the file name instead of

the Ivy artifact name. This is done because in case of Gradle

module metadata, the file name of an artifact is not necessarily

directly bound to the module name and causes comparison issues.

Use file names instea of Ivy artifact names for comparison

This commit reworks the generation of verification file and

verification itself in order to use the file name instead of

the Ivy artifact name. This is done because in case of Gradle

module metadata, the file name of an artifact is not necessarily

directly bound to the module name and causes comparison issues.

Use file names instea of Ivy artifact names for comparison

This commit reworks the generation of verification file and

verification itself in order to use the file name instead of

the Ivy artifact name. This is done because in case of Gradle

module metadata, the file name of an artifact is not necessarily

directly bound to the module name and causes comparison issues.