DefaultDependencyConstraintHandlerTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove the singleton `NamedObjectInstantiator`. This is now available as a global service instead.

    • -1
    • +2
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 13 more files in changeset.
Remove the singleton `NamedObjectInstantiator`. This is now available as a global service instead.

    • -1
    • +2
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 13 more files in changeset.
Remove the singleton `NamedObjectInstantiator`. This is now available as a global service instead.

    • -1
    • +2
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 13 more files in changeset.
Remove the singleton `NamedObjectInstantiator`. This is now available as a global service instead.

    • -1
    • +2
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 13 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -3
    • +1
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 21 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -2
    • +1
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 21 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -2
    • +1
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 21 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -3
    • +1
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 27 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -3
    • +1
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 27 more files in changeset.
Allow the services required by a given class to be queried prior to creating any instances of that class. Use this to allow `ArtifactTransformDependencies` to be injected into artifact transforms using any of the service injection patterns (that is, via a constructor or a getter).

    • -1
    • +1
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 127 more files in changeset.
Remove some direct usages of `AsmBackedClassGenerator` from tests, and instead use `TestUtil` fixture to take care of setting up a decorating `Instantiator`.

    • -2
    • +2
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 17 more files in changeset.
Add support for enforcing published platforms

This commit aligns the behavior of Gradle for published platforms

to the one for virtual platforms with regards to enforced behavior.

The implementation is pretty weak as it uses a component metadata

rule to update the dependencies/constraints of a platform, which

implies that the version used in the DSL is a fixed version.

    • -1
    • +3
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 13 more files in changeset.
Separate Dependency Constraint and Dependency declarations (#4255)

The interfaces for declaring these two different things were

coupled in the initial implementation - to reuse all functionality

based on the Dependency interface directly. This interface is used

internally to pass dependency declarations through the resolution

process. However, this is only due to remembering the first

level dependencies for the "old" results API

(Configuration.resolvedConfiguration()).

These implementation specifics should not bleed into the API.

A dependency declaration defines a *requirement*:

I require module/project X

A dependency constraint defines a *constraint*:

If I must use X, I can only work with versions matching the constraint

Only if we look at external dependencies, constraints and external dependencies

share the ability to declare a *version constraint*. Therefore, both now

extend ModuleVersionSelector.

Now, dependency constraints are removed as "first level dependencies"

from the result. This is fine as the dependency itself is still in the

result graph - when there is a constraint, there is always at least one other

edge.

    • -11
    • +11
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 33 more files in changeset.
Add dependency constraints DSL

This adds the DependencyConstraint and DependencyConstraintHandler types

with their implementations and wires them into the DependencyHandler.

    • -0
    • +204
    ./DefaultDependencyConstraintHandlerTest.groovy
  1. … 15 more files in changeset.