Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
WIP - Play with idea of `@DslMarker`

    • -0
    • +2
    ./DependencyConstraintHandlerDelegate.kt
  1. … 4 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 3 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

Issue #9907

  1. … 6 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 3 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 6 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

Issue #9907

  1. … 6 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 3 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 6 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 6 more files in changeset.
Add support for locking extension in ScriptHandler

This enables defining the lock mode and other extensions to dependency

locking.

  1. … 3 more files in changeset.
Fixes

Add a registry of shared "services" to the `Gradle` object. These are intended to be used by plugins to represent some service or state that is shared by tasks.

  1. … 11 more files in changeset.
Add a registry of shared "services" to the `Gradle` object. These are intended to be used by plugins to represent some service or state that is shared by tasks.

  1. … 12 more files in changeset.
Add a registry of shared "services" to the `Gradle` object. These are intended to be used by plugins to represent some service or state that is shared by tasks.

  1. … 11 more files in changeset.
Add a registry of shared "services" to the `Gradle` object. These are intended to be used by plugins to represent some service or state that is shared by tasks.

  1. … 12 more files in changeset.
Add a registry of shared "services" to the `Gradle` object. These are intended to be used by plugins to represent some service or state that is shared by tasks.

  1. … 12 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -6
    • +0
    ./DependencyConstraintHandlerDelegate.kt
  1. … 11 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -6
    • +0
    ./DependencyConstraintHandlerDelegate.kt
  1. … 9 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -6
    • +0
    ./DependencyConstraintHandlerDelegate.kt
  1. … 12 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -6
    • +0
    ./DependencyConstraintHandlerDelegate.kt
  1. … 9 more files in changeset.
Remove `platform` and `enforcePlatform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -12
    • +0
    ./DependencyConstraintHandlerDelegate.kt
  1. … 4 more files in changeset.
Remove `platform` and `enforcePlatform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -12
    • +0
    ./DependencyConstraintHandlerDelegate.kt
  1. … 3 more files in changeset.
Remove deprecation of classes still used by the IDE script templates

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.
Implement `Gradle` methods missing from `GradleDelegate`

Restore `PrecompiledInitScript` interface for backward compatibility

And do the same to `KotlinInitScript`, the script template used by the

IDE for content assistance.

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

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

    • -0
    • +44
    ./PluginAwareDelegate.kt
  1. … 11 more files in changeset.
wip: Remove `Gradle` and `Settings` interface delegation from Kotlin scripts

And take advantage of Kotlin script _implicit receivers_ instead.

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

And take advantage of Kotlin script _implicit receivers_ instead.

  1. … 13 more files in changeset.