Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Update upgrading guide

Update upgrading guide

Remove 'compare-gradle-builds' plugin from distribution (#10198)

* Remove non-public ProjectOutcomes model type

* Remove 'compare-gradle-builds' plugin from distribution

    • -1
    • +0
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
  1. … 126 more files in changeset.
Polish `Codec.kt`

Polish `Codec.kt`

Polish `Codec.kt`

Remove no longer necessary `SerializableReadReplaceReader`

Now that the `writeReplace` / `readResolve` responsibility was moved to `BeanCodec`.

Remove no longer necessary `SerializableReadReplaceReader`

Now that the `writeReplace` / `readResolve` responsibility was moved to `BeanCodec`.

Remove no longer necessary `SerializableReadReplaceReader`

Now that the `writeReplace` / `readResolve` responsibility was moved to `BeanCodec`.

Remove `CompatibilityAdapterForTaskInputs`

Remove `CompatibilityAdapterForTaskInputs`

Remove `CompatibilityAdapterForTaskInputs`

Remove `CompatibilityAdapterForTaskInputs`

Merge pull request #10200 from gradle/wolfs/deprecations/saveProperties

Remove deprecated GUtil.savePropertiesNoDateComment

Remove FindBugs and JDepend plugins from Gradle distribution

  1. … 50 more files in changeset.
Update upgrading guide

Update upgrading guide

Remove deprecated GUtil.savePropertiesNoDateComment

Remove deprecated GUtil.savePropertiesNoDateComment

Remove non-public ProjectOutcomes model type

Remove non-public ProjectOutcomes model type

A work node receives a context that exposes the build scoped services, rather than an empty registry, when the node is not associated with a project. This means that a node implementation does not have to carry build scoped services around in case it does not end up have an owning project, and can just locate the execution services it needs via its context when it runs.

A node receives a context that exposes the build scoped services, rather than an empty context, when the node is not associated with a project. This means that a node implementation does not have to carry services around in case it does not have an owning project, but can just locate the execution services it needs via its context.

A work node receives a context that exposes the build scoped services, rather than an empty registry, when the node is not associated with a project. This means that a node implementation does not have to carry build scoped services around in case it does not end up have an owning project, and can just locate the execution services it needs via its context when it runs.

A node receives a context that exposes the build scoped services, rather than an empty context, when the node is not associated with a project. This means that a node implementation does not have to carry services around in case it does not have an owning project, but can just locate the execution services it needs via its context.

Remove 'compare-gradle-builds' plugin from distribution

    • -1
    • +0
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
  1. … 116 more files in changeset.
Remove 'compare-gradle-builds' plugin from distribution

    • -1
    • +0
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
  1. … 115 more files in changeset.
Remove 'compare-gradle-builds' plugin from distribution

    • -1
    • +0
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
  1. … 115 more files in changeset.
Upgrade to build-scan-plugin 2.4-rc-1

Decouple work node implementations from projects a little, so that a node is given a context through which it can locate its execution services, rather than using a project service registry directly.

  1. … 6 more files in changeset.