Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix StackOverflow in SourceTask

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

Let SourceTask use a ConfigurableFileCollection

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

Make lib/plugins an input

  1. … 4 more files in changeset.
Fix indent

Co-Authored-By: Bo Zhang <bo@gradle.com>

Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 3 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 3 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 2 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 3 more files in changeset.
Replace password-based authentication with token in distributed performance tests

  1. … 8 more files in changeset.
Replace TeamCityRestBot

  1. … 8 more files in changeset.
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

  1. … 69 more files in changeset.
Disallow builds defining a project at :buildSrc

This is already prohibited by the composite build machinery if there is

also a real buildSrc project. This change makes the failure earlier and

more obvious.

  1. … 8 more files in changeset.
Synchronize access to build state registry in GradleBuild

  1. … 1 more file in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 7 more files in changeset.
A client module defining dependency declaration is always different

Ensure build paths are unique before using them

Also pushes uniqueness validation earlier

  1. … 7 more files in changeset.
Add TODO about allowing GradleBuild tasks to specify build path

Make paths/names of included builds immutable

  1. … 31 more files in changeset.
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use Java 8 syntax for copy-like tasks

    • -8
    • +5
    ./internal/file/copy/CopySpecWrapper.java
    • -1
    • +1
    ./internal/file/copy/DefaultCopySpec.java
  1. … 3 more files in changeset.
Rename field to fineGrainedInvalidationEnabled

Use real VFS

Not the implementation delegating to the file system snapshotter.

  1. … 2 more files in changeset.
Use real VFS

Not the implementation delegating to the file system snapshotter.

  1. … 2 more files in changeset.
Use real VFS

Not the implementation delegating to the file system snapshotter.

  1. … 2 more files in changeset.
Use real VFS

Not the implementation delegating to the file system snapshotter.

  1. … 2 more files in changeset.
Use real VFS

Not the implementation delegating to the file system snapshotter.

  1. … 2 more files in changeset.