Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge pull request #10286 from gradle/devisnk/make-detached-config-name-thread-safe

Use AtomicInteger for detached configuration name counter

Merge pull request #9353 from gradle/jjohannes/deprecate-java-configurations

Deprecate legacy configuration usages

Use AtomicInteger for detached configuration name counter

Signed-off-by: Volker Leck <volker@gradle.com>

Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

  1. … 1 more file in changeset.
Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

  1. … 2 more files in changeset.
Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

Deprecate legacy Java plugin configurations

  1. … 5 more files in changeset.
Deprecate legacy Java plugin configurations

  1. … 5 more files in changeset.
Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

Do not ignore external artifacts when scheduling artifact transforms at task graph building time, if they happen to be known at that time. This was an accidental breakage in a previous change. Instead, run the transforms for external artifacts when serializing file collections to the instant execution cache and persist the transformation nodes only for project artifacts.

Do not ignore external artifacts when scheduling artifact transforms at task graph building time, if they happen to be known at that time. This was an accidental breakage in a previous change. Instead, run the transforms for external artifacts when serializing file collections to the instant execution cache and persist the transformation nodes only for project artifacts.

Merge pull request #10270 from gradle/lptr/execution/use-deleter-take-3

Use Deleter in more places, take 3

Move Deleter interface out of impl package

  1. … 41 more files in changeset.
Move Deleter interface out of impl package

  1. … 38 more files in changeset.
Give `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 9 more files in changeset.
Give `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 9 more files in changeset.
Given `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 7 more files in changeset.
Given `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 7 more files in changeset.
Given `ActionNode` and `TransformNode` a common `execute()` method and merge their `NodeExecutor` implementations.

  1. … 7 more files in changeset.
Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

  1. … 5 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

  1. … 6 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

  1. … 6 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

  1. … 6 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

  1. … 5 more files in changeset.
Fix constraint inheritance when the incoming edge itself is inheriting

  1. … 2 more files in changeset.
Add 'inheritConstraints' to Gradle Module Metadata

Adds test coverage for consuming and publishing.

  1. … 12 more files in changeset.