Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -2
    • +2
    ./NativeAlignmentWithJavaPlatformResolveIntegrationTest.groovy
  1. … 872 more files in changeset.
Desugar producer attribute if the requesting attribute is desugared (#11372)

This can be the case if an attribute on a dependency is published

and the resolved target of the dependency is a local project.

For example, a published platform dependency to a local java-platform

project.

We support 'Named' and 'Enum' for desugaring as that are the only

non-primitve types we currently allow to be published in Gradle

Module Metadata.

    • -2
    • +40
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Desugar producer attribute if the requesting attribute is desugared

This can be the case if a attribute on a dependency is published

and the resolved target of the dependency is a local project.

For example, a published platform dependency to a local java-platform

project.

    • -2
    • +40
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Desugar producer attribute if the requesting attribute is desugared

This can be the case if a attribute on a dependency is published

and the resolved target of the dependency is a local project.

For example, a published platform dependency to a local java-platform

project.

We support 'Named' and 'Enum' for desugaring as that are the only

non-primimitve types we currently allow to be published in Gradle

Module Metadata.

    • -2
    • +40
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Desugar producer attribute if the requesting attribute is desugared

This can be the case if a attribute on a dependency is published

and the resolved target of the dependency is a local project.

For example, a published platform dependency to a local java-platform

project.

    • -2
    • +40
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Desugar producer attribute if the requesting attribute is desugared

This can be the case if a attribute on a dependency is published

and the resolved target of the dependency is a local project.

For example, a published platform dependency to a local java-platform

project.

We support 'Named' and 'Enum' for desugaring as that are the only

non-primimitve types we currently allow to be published in Gradle

Module Metadata.

    • -2
    • +40
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +2
    ./NativeAlignmentWithJavaPlatformResolveIntegrationTest.groovy
  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +2
    ./NativeAlignmentWithJavaPlatformResolveIntegrationTest.groovy
  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +2
    ./NativeAlignmentWithJavaPlatformResolveIntegrationTest.groovy
  1. … 93 more files in changeset.
There can be multiple enforced platform variants for Gradle metadata

Follow up to: #11118

    • -8
    • +18
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
There can be multiple enforced platform variants for Gradle metadata

Follow up to: #11118

    • -8
    • +18
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 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"

}

}

    • -2
    • +2
    ./JavaPlatformResolveIntegrationTest.groovy
  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"

}

}

    • -2
    • +2
    ./JavaPlatformResolveIntegrationTest.groovy
  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"

}

}

    • -2
    • +2
    ./JavaPlatformResolveIntegrationTest.groovy
  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"

}

}

    • -2
    • +2
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +89
    ./JavaPlatformResolveIntegrationTest.groovy
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +89
    ./JavaPlatformResolveIntegrationTest.groovy
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"

}

}

    • -2
    • +2
    ./JavaPlatformResolveIntegrationTest.groovy
  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"

}

}

    • -2
    • +2
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 3 more files in changeset.
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +84
    ./JavaPlatformResolveIntegrationTest.groovy
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +84
    ./JavaPlatformResolveIntegrationTest.groovy
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +89
    ./JavaPlatformResolveIntegrationTest.groovy
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +84
    ./JavaPlatformResolveIntegrationTest.groovy
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -15
    • +20
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -15
    • +20
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -15
    • +20
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -15
    • +20
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 13 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -15
    • +20
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -15
    • +20
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 19 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -3
    • +3
    ./JavaPlatformResolveIntegrationTest.groovy
    • -1
    • +0
    ./NativeAlignmentWithJavaPlatformResolveIntegrationTest.groovy
  1. … 94 more files in changeset.