Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove no longer needed `InstantExecutionPropertiesLoader`

Remove no longer needed `InstantExecutionPropertiesLoader`

Remove no longer needed `InstantExecutionPropertiesLoader`

Serialize the task output `upToDateWhen` spec, if present, to the instant execution cache.

  1. … 5 more files in changeset.
Serialize the task output `upToDateWhen` spec, if present, to the instant execution cache.

  1. … 3 more files in changeset.
Serialize the task output `upToDateWhen` spec, if present, to the instant execution cache.

  1. … 5 more files in changeset.
Serialize the task output `upToDateWhen` spec, if present, to the instant execution cache.

  1. … 3 more files in changeset.
Don't use valid task name characters as meta characters in the ie cache key

Fix for previous commit.

  1. … 1 more file in changeset.
Fix for previous commit.

  1. … 1 more file in changeset.
Change `Provider.map()` and `Provider.flatMap()` to allow `null` to be returned by the mapping function.

  1. … 16 more files in changeset.
Change `Provider.map()` and `Provider.flatMap()` to allow `null` to be returned by the mapping function.

  1. … 16 more files in changeset.
Preserve cache key format when there are no excluded task names

Polish `DefaultInstantExecution`

Add excluded task names to the instant execution cache key

Add relative invocation dir to the instant execution cache key as needed

Because relative task names are resolved relative to the enclosing subproject

according to the invocation dir (`StartParameter.currentDir`).

  1. … 5 more files in changeset.
Polish `DefaultInstantExecution`

Let instant execution honor the build layout

  1. … 1 more file in changeset.
Introduce `providers.gradleProperty(propertyNameOrProvider)`

For automatically tracking Gradle properties used as build logic inputs.

  1. … 8 more files in changeset.
Introduce `providers.gradleProperty(propertyNameOrProvider)`

For automatically tracking Gradle properties used as build logic inputs.

  1. … 7 more files in changeset.
Use `LazyThreadSafetyMode.NONE` for lazy values used by single-threaded code

    • -0
    • +26
    ./kotlin/org/gradle/instantexecution/extensions/unsafeLazy.kt
Move system property access to `InstantExecutionStartParameter`

Load Gradle properties before checking instant execution fingerprint

  1. … 1 more file in changeset.
Fix previous commit.

Fix previous commit.

Partially fix the `jar` task with instant execution when the project has no source files or resources.

In this change, generate a placeholder manifest file for the Jar if it does not exist so as to ensure that the Jar file is generated. This will be improved later, so that the correct manifest content is included in the Jar.

  1. … 5 more files in changeset.
Partially fix the `jar` task with instant execution when the project has no source files or resources.

In this change, generate a placeholder manifest file for the Jar if it does not exist so as to ensure that the Jar file is generated. This will be improved later, so that the correct manifest content is included in the Jar.

  1. … 4 more files in changeset.
Partially fix the `jar` task with instant execution when the project has no source files or resources.

In this change, generate a placeholder manifest file for the Jar if it does not exist so as to ensure that the Jar file is generated. This will be improved later, so that the correct manifest content is included in the Jar.

  1. … 4 more files in changeset.
Partially fix the `jar` task with instant execution when the project has no source files or resources.

In this change, generate a placeholder manifest file for the Jar if it does not exist so as to ensure that the Jar file is generated. This will be improved later, so that the correct manifest content is included in the Jar.

  1. … 5 more files in changeset.
Get `--scan` to work with instant execution again

By making the `Settings` object initialization in instant execution more similar

to how it works in classic execution:

- instantiate `Settings` object during `SettingsPreparer` execution

- move `SettingsProcessor` execution to happen in the context of `SettingsPreparer`

- create a separate ClassLoaderScope for `Settings` so it can receive plugins

- always apply auto-applied plugin requests during `SettingsProcess` execution

This commit also removes the system property propagation hack as it's no longer

needed.

  1. … 1 more file in changeset.