TestProjectSelectorState.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 6 more files in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 6 more files in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 6 more files in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 6 more files in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 7 more files in changeset.
Track first dependency artifact in SelectorState and ModuleSelectors

This information needs to be preserved to make sure that an artifact

that acts as metadata for itself (metadataSources = artifact()) is

found during the early resolution phase where we search for modules

in repositories.

  1. … 4 more files in changeset.
Track first dependency artifact in SelectorState and ModuleSelectors

This information needs to be preserved to make sure that an artifact

that acts as metadata for itself (metadataSources = artifact()) is

found during the early resolution phase where we search for modules

in repositories.

  1. … 4 more files in changeset.
Track first dependency artifact in SelectorState and ModuleSelectors

This information needs to be preserved to make sure that an artifact

that acts as metadata for itself (metadataSources = artifact()) is

found during the early resolution phase where we search for modules

in repositories.

  1. … 4 more files in changeset.
Track first dependency artifact in SelectorState and ModuleSelectors

This information needs to be preserved to make sure that an artifact

that acts as metadata for itself (metadataSources = artifact()) is

found during the early resolution phase where we search for modules

in repositories.

  1. … 4 more files in changeset.
Collect all dependency artifacts in SelectorState and ModuleSelectors

This information needs to be preserved to make sure that an artifact

that acts as metadata for itself (metadataSources = artifact()) is

found during the early resolution phase where er search for modules

in repositories.

  1. … 4 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 23 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 18 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 23 more files in changeset.
Fix alignement of forced platforms on patch versions

This commit fixes the behavior of alignement whenever the

platform version is a patch version, and that not all modules

are available in that patch version. Previously, alignement

would be defeated. With this change, we will do our best to

align to the highest seen version in the graph for each of

the modules.

Fixes nebula-plugins/gradle-nebula-integration#51

  1. … 8 more files in changeset.
Fix dependency locking with `latest.*` and `*.+` selectors

Instead of making these particular selectors behave differently when locking is enabled,

we now use the fact that the candidate version comes from a lock to decide if it can be

used as a "better version" to satisfy a `latest.*` or `*.+` selector.

Fixes #6340

  1. … 10 more files in changeset.
Tidy up implementation of SelectorStateResolver

  1. … 3 more files in changeset.
Support a dependency with both `require` and `prefer` versions

  1. … 14 more files in changeset.
Mark empty selectors failed in case resolution fails

Changes that skipped empty selectors caused them to end in a resolved

state without a failure nor a selected target component. This commit

fixes the failure case as it was causing a NPE during failure

collection.

Fixes #6675

  1. … 6 more files in changeset.
Clarify test coverage for project selector state

This unit test was verifying the abstract case where the

`ResolvedVersionConstraint` is null for a Selector State.

This behaviour is limited to local project selectors, so the test has

been updated to be more representative.

    • -0
    • +63
    ./TestProjectSelectorState.groovy
  1. … 6 more files in changeset.