DependencyConstraintHandlerDelegate.kt

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.
Simplify sentence in documentation comment

    • -1
    • +1
    ./DependencyConstraintHandlerDelegate.kt
  1. … 8 more files in changeset.
Rename `o.g.k.dsl.decorators.*Decorator` to `o.g.k.dsl.delegates.*Delegate`

    • -0
    • +57
    ./DependencyConstraintHandlerDelegate.kt
  1. … 25 more files in changeset.