Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Uniformly use RepoScriptBlockUtil in Kotlin DSL tests

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

  1. … 4 more files in changeset.
Polish `KotlinSettingsScriptIntegrationTest`

Let compiled Kotlin script templates implement `PluginAware` by delegation

In order to enable `ObjectConfigurationAction` syntax (`apply {... }`)

and to preserve file resolving semantics when using a `PluginAware`

extension such as `PluginAware.apply(from: String? = null, ...)` -

init and settings scripts resolve the applied script file relative to

the applying script.

  1. … 5 more files in changeset.
Disable deprecation checks for some Kotlin tests

  1. … 5 more files in changeset.
Disable deprecation checks for some Kotlin tests

  1. … 5 more files in changeset.
Disable deprecation checks for some Kotlin tests

  1. … 5 more files in changeset.
Disable deprecation checks for some Kotlin tests

  1. … 5 more files in changeset.
Disable deprecation checks for some Kotlin tests

  1. … 5 more files in changeset.
Replace `Project` interface delegation by `Project` implicit receiver

  1. … 12 more files in changeset.
Replace `Project` interface delegation by `Project` implicit receiver

  1. … 12 more files in changeset.
wip: Remove `Gradle` and `Settings` interface delegation from Kotlin scripts

And take advantage of Kotlin script _implicit receivers_ instead.

    • -24
    • +45
    ./dsl/resolver/KotlinScriptDependenciesResolverTest.kt
  1. … 13 more files in changeset.
Remove `Gradle` and `Settings` interface delegation from Kotlin scripts

And take advantage of Kotlin script _implicit receivers_ instead.

    • -24
    • +45
    ./dsl/resolver/KotlinScriptDependenciesResolverTest.kt
  1. … 14 more files in changeset.
Change tests not to expect Kotlin scripts to implement `Gradle`, `Settings` or `Project`

    • -8
    • +12
    ./dsl/resolver/KotlinScriptDependenciesResolverTest.kt
Add coverage for conflict with pinned embedded kotlin

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

Add coverage for conflict with pinned embedded kotlin

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

Polish EmbeddedKotlinProviderTest

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

Pin the whole subgraph of embedded kotlin dependencies

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

  1. … 3 more files in changeset.
Pin the whole subgraph of embedded kotlin dependencies

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

  1. … 3 more files in changeset.
Remove the embedded-kotlin-repository

It was based on ClientModule dependencies that caused more troubles than

anything. The main one being that the artificial dependency graph needed

to be kept up to date with each Kotlin version. Moreover since several

Kotlin versions, declaring a repository is necessary in any case. This

change simplifies the code and should make the runtime a bit faster.

However, the Kotlin dependencies when applying the `kotlin-dsl` plugin

are now required to be downloaded. This isn't a big change and should

only impact people using the `kotlin-dsl` plugin without depending on

Kotlin in other parts of their build. This could be alleviated in the

future if dependency resolution considers the Gradle install/distro as a

source of artifacts in the same way it uses maven local.

Along the way, the pinning of Kotlin dependencies to the embedded

version for the build scripts classpath has been moved from a resolution

rule to proper, faster, dependency constraints.

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

  1. … 6 more files in changeset.
Remove the embedded-kotlin-repository

It was based on ClientModule dependencies that caused more troubles than

anything. The main one being that the artificial dependency graph needed

to be kept up to date with each Kotlin version. Moreover since several

Kotlin versions, declaring a repository is necessary in any case. This

change simplifies the code and should make the runtime a bit faster.

However, the Kotlin dependencies when applying the `kotlin-dsl` plugin

are now required to be downloaded. This isn't a big change and should

only impact people using the `kotlin-dsl` plugin without depending on

Kotlin in other parts of their build. This could be alleviated in the

future if dependency resolution considers the Gradle install/distro as a

source of artifacts in the same way it uses maven local.

Along the way, the pinning of Kotlin dependencies to the embedded

version for the build scripts classpath has been moved from a resolution

rule to proper, faster, dependency constraints.

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

  1. … 6 more files in changeset.
Remove the embedded-kotlin-repository

It was based on ClientModule dependencies that caused more troubles than

anything. The main one being that the artificial dependency graph needed

to be kept up to date with each Kotlin version. Moreover since several

Kotlin versions, declaring a repository is necessary in any case. This

change simplifies the code and should make the runtime a bit faster.

However, the Kotlin dependencies when applying the `kotlin-dsl` plugin

are now required to be downloaded. This isn't a big change and should

only impact people using the `kotlin-dsl` plugin without depending on

Kotlin in other parts of their build. This could be alleviated in the

future if dependency resolution considers the Gradle install/distro as a

source of artifacts in the same way it uses maven local.

Along the way, the pinning of Kotlin dependencies to the embedded

version for the build scripts classpath has been moved from a resolution

rule to proper, faster, dependency constraints.

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

  1. … 6 more files in changeset.
Add missing dependency to embedded kotlin

* kotlin-stdlib now depends on kotlin-stdlib-common, this was not

reflected in the setup of the embedded kotlin repo.

* A way to experience this issue was with locking on a kotlin-dsl

project.

Fixes #10697

  1. … 1 more file in changeset.
Fix some Kotlin tests

  1. … 5 more files in changeset.
Fix some Kotlin tests

  1. … 6 more files in changeset.