Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make query methods for deprecation state of core configurations public

This is to allow plugin authors to make use of this information.

The methods to actually deprecate configurations stay internal,

as they are bound to the deprecation mechanism of Gradle core.

And thus they may only be used for configurations of Gradle's core

plugins.

  1. … 12 more files in changeset.
Make query methods for deprecation state of core configurations public

This is to allow plugin authors to make use of this information.

The methods to actually deprecate configurations stay internal,

as they are bound to the deprecation mechanism of Gradle core.

And thus they may only be used for configurations of Gradle's core

plugins.

  1. … 12 more files in changeset.
Tweak messages for previous commit, fixes.

  1. … 11 more files in changeset.
Add `BuildServiceParameters.None` marker type that is used to indicate that a build service does not take any parameters, to match the pattern used in other places.

Extract some validation logic from several places so it can be reused in the places where parameterized isolated objects, such as artifact transforms or build services, are registered.

  1. … 35 more files in changeset.
Add `BuildServiceParameters.None` marker type that is used to indicate that a build service does not take any parameters, to match the pattern used in other places.

Extract some validation logic from several places so it can be reused in the places where parameterized isolated objects, such as artifact transforms or build services, are registered.

  1. … 35 more files in changeset.
Handle serialization for shadowed capabilities in the GMM case (#11179)

This is now done in the same way as it is done in the

AbstractRealisedModuleResolveMetadataSerializationHelper

for cases without GMM

Follow up to: #11118

  1. … 4 more files in changeset.
Handle serialization for shadowed capabilities in the GMM case

This is now done in the same way as it is done in the

AbstractRealisedModuleResolveMetadataSerializationHelper

for cases without GMM

Follow up to: #11118

  1. … 4 more files in changeset.
There can be multiple enforced platform variants for Gradle metadata

Follow up to: #11118

  1. … 3 more files in changeset.
There can be multiple enforced platform variants for Gradle metadata

Follow up to: #11118

  1. … 3 more files in changeset.
Increase cache layout version

  1. … 1 more file in changeset.
Increase cache layout version

  1. … 1 more file in changeset.
Increase cache layout version

  1. … 1 more file 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"

}

}

  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"

}

}

  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"

}

}

  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"

}

}

  1. … 9 more files in changeset.
Fix NPE and tests

  1. … 4 more files in changeset.
Fix NPE and tests

  1. … 3 more files in changeset.
Increase cache layout version

  1. … 1 more file in changeset.
Increase cache layout version

  1. … 1 more file in changeset.
Increase cache layout version

  1. … 1 more file in changeset.
Use a different 'shadow capability' for enforced platform

This allows both 'regular' and 'enforced' platform of the same

component to be selected. In order to make this work, support

for projects having shadow capability needed to be added.

  1. … 10 more files in changeset.
Always apply all Category disambiguation rules

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, other consumers

may also require all rules (see #11091)

  1. … 5 more files in changeset.
Always apply all Category disambiguation rules

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, other consumers

may also require all rules (see #11091)

  1. … 5 more files in changeset.
Introduce new metadata marker for Gradle 6 (#11109)

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

  1. … 13 more files in changeset.
Always apply all Category disambiguation rules in Java ecosystem

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, consumers using other

Java plugins may also require all rules (see #11091)

  1. … 4 more files in changeset.
Introduce new metadata marker for Gradle 6

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

  1. … 13 more files in changeset.
Introduce new metadata marker for Gradle 6

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

  1. … 13 more files in changeset.
Introduce new metadata marker for Gradle 6

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

  1. … 10 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 17 more files in changeset.