Clone
 

adam murdoch <adam@gradle.com> in Gradle

Remove old build service registration method.

Use new build service registation method in `AvailableJavaInstallationsPlugin`.

Upgrade to new Gradle nightly.

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Move the functional tests for concurrent usage of build services into a separate test class, and fix for instant execution.

Move the functional tests for concurrent usage of build services into a separate test class, and fix for instant execution.

Move the functional tests for concurrent usage of build services into a separate test class, and fix for instant execution.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Add a method to `Task` to allow runtime registration of the services that the task will use.

This is intended really just to be a placeholder for some kind of API where the usage can be declared.

Remove the `requiresResource()` methods from `AbstractTask`. In particular, remove the ability to express "how much" of the resource the task will use. For now, assume that usage by each task has equal weight.

Add a method to `Task` to allow runtime registration of the services that the task will use.

This is intended really just to be a placeholder for some kind of API where the usage can be declared.

Remove the `requiresResource()` methods from `AbstractTask`. In particular, remove the ability to express "how much" of the resource the task will use. For now, assume that usage by each task has equal weight.

Add a method to `Task` to allow runtime registration of the services that the task will use.

This is intended really just to be a placeholder for some kind of API where the usage can be declared.

Remove the `requiresResource()` methods from `AbstractTask`. In particular, remove the ability to express "how much" of the resource the task will use. For now, assume that usage by each task has equal weight.

Add a method to `Task` to allow runtime registration of the services that the task will use.

This is intended really just to be a placeholder for some kind of API where the usage can be declared.

Remove the `requiresResource()` methods from `AbstractTask`. In particular, remove the ability to express "how much" of the resource the task will use. For now, assume that usage by each task has equal weight.

Test fixes for previous commit.

Test fixes for previous commit.

Test fixes for previous commit.

Move the task-specific logic that determines the resources used by a task out of `DefaultExecutionPlan` and into the node implementations.

Most of this logic moves into `AbstractTask` and `DefaultBuildServiceRegistry` and the node deletegates to these.

Move the task-specific logic that determines the resources used by a task out of `DefaultExecutionPlan` and into the node implementations.

Most of this logic moves into `AbstractTask` and `DefaultBuildServiceRegistry` and the node deletegates to these.

Move the task-specific logic to determine the resources used by a task out of `DefaultExecutionPlan` and into the node implementations.

Most of this logic moves into `AbstractTask` and `DefaultBuildServiceRegistry`.

Move the task-specific logic to determine the resources used by a task out of `DefaultExecutionPlan` and into the node implementations.

Most of this logic moves into `AbstractTask` and `DefaultBuildServiceRegistry`.

Move the task-specific logic to determine the resources used by a task out of `DefaultExecutionPlan` and into the node implementations.

Most of this logic moves into `AbstractTask` and `DefaultBuildServiceRegistry`.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.