Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Upgrade Kotlin to 1.3.60

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

    • -4
    • +5
    ./kotlin/dsl/execution/InterpreterTest.kt
  1. … 4 more files in changeset.
Fix for previous commit.

    • -4
    • +5
    ./kotlin/dsl/execution/InterpreterTest.kt
  1. … 4 more files in changeset.
Fix `ClassNotFoundExeception` when loading objects whose class is defined in a build script from the instant execution cache, after recreating the cache from a daemon process that has previously successfully used the cache.

For example, running `gradle taskA`, `gradle taskA`, `gradle taskB`, `gradle taskB` would fail if `taskB` uses types from a build script.

This was happening because the script ClassLoaders are cached and reused, but the association between ClassLoader and scope was lost, and this association is what instant execution uses to know how to load the class.

This change fixes one case of this problem, but the same problem can still happen if the set of build scripts being referenced changes.

    • -4
    • +5
    ./kotlin/dsl/execution/InterpreterTest.kt
  1. … 25 more files in changeset.
Fix `ClassNotFoundExeception` when loading objects whose class is defined in a build script from the instant execution cache, after recreating the cache from a daemon process that has previously successfully used the cache.

For example, running `gradle taskA`, `gradle taskA`, `gradle taskB`, `gradle taskB` would fail if `taskB` uses types from a build script.

This was happening because the script ClassLoaders are cached and reused, but the association between ClassLoader and scope was lost, and this association is what instant execution uses to know how to load the class.

This change fixes one case of this problem, but the same problem can still happen if the set of build scripts being referenced changes.

    • -4
    • +5
    ./kotlin/dsl/execution/InterpreterTest.kt
  1. … 25 more files in changeset.
Ensure `settings.gradle.kts` with `pluginManagement` block honors auto-applied plugins

Make `settings.gradle.kts` evaluation trigger auto-applied plugins

  1. … 1 more file in changeset.
Polish `ScriptApiTest`

    • -1
    • +1
    ./kotlin/dsl/provider/ScriptApiTest.kt
Polish `ScriptApiTest`

    • -1
    • +1
    ./kotlin/dsl/provider/ScriptApiTest.kt
Polish `ScriptApiTest`

    • -1
    • +1
    ./kotlin/dsl/provider/ScriptApiTest.kt
Polish `ScriptApiTest`

    • -1
    • +1
    ./kotlin/dsl/provider/ScriptApiTest.kt
Migrate Kotlin DSL IDE Settings script template to new API

    • -10
    • +0
    ./kotlin/dsl/provider/ScriptApiTest.kt
  1. … 5 more files in changeset.
Migrate Kotlin DSL IDE Settings script template to new API

    • -10
    • +0
    ./kotlin/dsl/provider/ScriptApiTest.kt
  1. … 5 more files in changeset.
Migrate Kotlin DSL IDE Settings script template to new API

    • -10
    • +0
    ./kotlin/dsl/provider/ScriptApiTest.kt
  1. … 5 more files in changeset.
Migrate Kotlin DSL IDE Settings script template to new API

    • -10
    • +0
    ./kotlin/dsl/provider/ScriptApiTest.kt
  1. … 5 more files in changeset.
Integrate with Gradle Enterprise plugin 3.0 (#11041)

    • -7
    • +7
    ./kotlin/dsl/PluginDependenciesSpecScopeTest.kt
  1. … 52 more files in changeset.
Fix test

    • -4
    • +4
    ./kotlin/dsl/PluginDependenciesSpecScopeTest.kt
  1. … 1 more file in changeset.
Update scan support for Gradle Enterprise plugin 3.0

Gradle 6 is now only compatible with this plugin.

    • -4
    • +4
    ./kotlin/dsl/PluginDependenciesSpecScopeTest.kt
  1. … 35 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. … 72 more files in changeset.
Make paths/names of included builds immutable

  1. … 32 more files in changeset.
Upgrade embedded Kotlin to 1.3.60-eap-23

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

  1. … 3 more files in changeset.
Upgrade embedded Kotlin to 1.3.60-eap-23

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

  1. … 3 more files in changeset.
Upgrade embedded Kotlin to 1.3.60-eap-23

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

  1. … 3 more files in changeset.
Upgrade embedded Kotlin to 1.3.60-eap-23

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

  1. … 3 more files in changeset.
Polish ResolverCoordinatorTest

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

Polish ResolverCoordinatorTest

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

Prefer `Action<T>` over `T.() -> Unit` for the Kotlin script API

From the perspective of an user of the API both types are effectively

the same.

From a compile time and runtime perspective `Action<T>` seems a better

choice as values can be passed to the core Gradle API directly.

From an API consistency point of view `Action<T>` also looks like the

superior choice as it is more consistent with the rest of the Gradle

API.

And finally, from an user education perspective, `KotlinScript`

provides a clear opportunity for users to understand the equivalence

between `Action<T>` and `T.() -> Unit`.

    • -3
    • +3
    ./kotlin/dsl/provider/ScriptApiTest.kt
  1. … 2 more files in changeset.
Polish `ScriptApiTest`

    • -5
    • +4
    ./kotlin/dsl/provider/ScriptApiTest.kt
Polish `ResidualProgramCompilerTest`

- Remove spurious empty line

Remove `ScriptApi` interface and use `KotlinScript` instead

    • -2
    • +4
    ./kotlin/dsl/provider/ScriptApiTest.kt
  1. … 1 more file in changeset.