Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix errors in the single version description

  1. … 2 more files in changeset.
Further invalid dependency declaration

* Prevent combining artifact and target configuration declaration

Fixes #10532

  1. … 2 more files in changeset.
Further invalid dependency declaration

* Prevent combining artifact and target configuration declaration

Fixes #10532

  1. … 3 more files in changeset.
Further invalid dependency declaration

* Prevent combining artifact and target configuration declaration

Fixes #10532

  1. … 3 more files in changeset.
Further invalid dependency declaration

* Prevent combining artifact and target configuration declaration

Fixes #10532

  1. … 2 more files in changeset.
Introduce shorthand notation for strict versions

This commit introduces a modifier (!!) that can be

used in version strings to introduce a strict version.

For example, the following notation:

org:foo:1.0!!

is equivalent to:

version { strictly '1.0' }

And this notation:

org:foo:[1.0,2.0]!!1.5

is equivalent to:

version {

strictly '[1.0, 2.0]'

prefer '1.5'

}

    • -2
    • +40
    ./notations/DependencyStringNotationConverterTest.groovy
  1. … 2 more files in changeset.
Fix test

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. … 22 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. … 17 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. … 22 more files in changeset.
Use "real" cache layout version

  1. … 1 more file in changeset.
Support prefix and latest selectors in strictly

This was basically just about adding test coverage.

The assumed behavior is that `latest.release` would

accept _any_ version when used in a reject selector,

so that we can iterate on rejected versions until

we find a match.

    • -18
    • +10
    ./artifacts/dependencies/DefaultResolvedVersionConstraintTest.groovy
  1. … 3 more files in changeset.
Support prefix and latest selectors in strictly

This was basically just about adding test coverage.

The assumed behavior is that `latest.release` would

accept _any_ version when used in a reject selector,

so that we can iterate on rejected versions until

we find a match.

    • -18
    • +10
    ./artifacts/dependencies/DefaultResolvedVersionConstraintTest.groovy
  1. … 3 more files in changeset.
Fix inconsistent dependency graph state

This commit fixes a problem with _unattached dependencies_ being

incorrectly removed from the dependency graph whenever only the

target of an edge is changed.

This was causing the Gradleception build to fail with strict

dependencies as "forSubgraph", but the problem was already

present (and left unnoticed).

  1. … 5 more files in changeset.
Fix inconsistent dependency graph state

This commit fixes a problem with _unattached dependencies_ being

incorrectly removed from the dependency graph whenever only the

target of an edge is changed.

This was causing the Gradleception build to fail with strict

dependencies as "forSubgraph", but the problem was already

present (and left unnoticed).

  1. … 5 more files in changeset.
Fix inconsistent dependency graph state

This commit fixes a problem with _unattached dependencies_ being

incorrectly removed from the dependency graph whenever only the

target of an edge is changed.

This was causing the Gradleception build to fail with strict

dependencies as "forSubgraph", but the problem was already

present (and left unnoticed).

  1. … 5 more files in changeset.
Fix inconsistent dependency graph state

This commit fixes a problem with _unattached dependencies_ being

incorrectly removed from the dependency graph whenever only the

target of an edge is changed.

This was causing the Gradleception build to fail with strict

dependencies as "forSubgraph", but the problem was already

present (and left unnoticed).

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

Required for serialization changes in #10368

  1. … 1 more file in changeset.
Support adding variants and files in component metadata rules (#10368)

Support adding variants and files in component metadata rules

  1. … 2 more files in changeset.
Bump metadata format

There was a conflict due to 2 different PRs bumping to the save

version at the same time.

  1. … 1 more file in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

  1. … 29 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

  1. … 29 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

  1. … 29 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

  1. … 29 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

  1. … 29 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

    • -12
    • +8
    ./artifacts/ModuleComponentSelectorSerializerTest.groovy
    • -17
    • +12
    ./artifacts/dependencies/DefaultImmutableVersionConstraintTest.groovy
    • -24
    • +0
    ./artifacts/dependencies/DefaultMutableVersionConstraintTest.groovy
  1. … 70 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).

    • -12
    • +8
    ./artifacts/ModuleComponentSelectorSerializerTest.groovy
    • -17
    • +12
    ./artifacts/dependencies/DefaultImmutableVersionConstraintTest.groovy
    • -24
    • +0
    ./artifacts/dependencies/DefaultMutableVersionConstraintTest.groovy
  1. … 69 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).

    • -12
    • +8
    ./artifacts/ModuleComponentSelectorSerializerTest.groovy
    • -17
    • +12
    ./artifacts/dependencies/DefaultImmutableVersionConstraintTest.groovy
    • -24
    • +0
    ./artifacts/dependencies/DefaultMutableVersionConstraintTest.groovy
  1. … 69 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).

    • -12
    • +8
    ./artifacts/ModuleComponentSelectorSerializerTest.groovy
    • -17
    • +12
    ./artifacts/dependencies/DefaultImmutableVersionConstraintTest.groovy
    • -24
    • +0
    ./artifacts/dependencies/DefaultMutableVersionConstraintTest.groovy
  1. … 69 more files in changeset.