IvyResolveIntegrationTest.groovy

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>

  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

  1. … 93 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).

  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).

  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).

  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).

  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).

  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).

  1. … 77 more files in changeset.
Adjust tests and samples to new metadata sources defaults

  1. … 95 more files in changeset.
wip - fix more tests

  1. … 46 more files in changeset.
wip - fix more tests

  1. … 45 more files in changeset.
wip - fix more tests

  1. … 46 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

  1. … 4 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

  1. … 4 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

  1. … 4 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

  1. … 4 more files in changeset.
Use doLast instead of left shift operator

Made this change in preparation for deprecating the left shift operator.

+review REVIEW-6236

    • -46
    • +60
    ./IvyResolveIntegrationTest.groovy
  1. … 163 more files in changeset.
Renamed subprojects/core-impl to subprojects/dependency-management.

    • -0
    • +276
    ./IvyResolveIntegrationTest.groovy
  1. … 1384 more files in changeset.