SubgraphVersionConstraintsIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -761
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -761
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 79 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -761
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -761
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -761
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -761
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 77 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -5
    • +5
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 95 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -5
    • +5
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -5
    • +5
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -5
    • +5
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 32 more files in changeset.
Do not fail early on conflict: let conflict resolution kick in

    • -3
    • +24
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
A version constraint with isForSubgraph() is not requiredOnly()

    • -18
    • +23
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 2 more files in changeset.
A version constraint with isForSubgraph() is not requiredOnly()

    • -18
    • +23
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix ancestor collection for subgraph constraints

We need to compute the intersection of constraints.

    • -0
    • +135
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix ancestor collection for subgraph constraints

We need to compute the intersection of constraints.

    • -0
    • +135
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix ancestor collection for subgraph constraints

We need to compute the intersection of constraints.

    • -0
    • +135
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix ancestor collection for subgraph constraints

We need to compute the intersection of constraints.

    • -0
    • +135
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
Move subgraph with substitution rule to SubgraphVersionConstraintsFeatureInteractionIntegrationTest

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

    • -66
    • +0
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
SubgraphVersionConstraintsIntegrationTest: add test for downgrade dependency when substitution rule is present

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

    • -0
    • +66
    ./SubgraphVersionConstraintsIntegrationTest.groovy
Add integration tests for subgraph version constraints

    • -0
    • +600
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 2 more files in changeset.
Add integration tests for subgraph version constraints

    • -0
    • +600
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 2 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +522
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 7 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +522
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 7 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +522
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 6 more files in changeset.
[Spike] Implementation based on conflict resolution

    • -11
    • +13
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 7 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +430
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 5 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +430
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 7 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +430
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 6 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -0
    • +430
    ./SubgraphVersionConstraintsIntegrationTest.groovy
  1. … 7 more files in changeset.