Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

    • -3
    • +0
    ./AbstractExternalModuleDependency.java
  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

    • -3
    • +0
    ./AbstractExternalModuleDependency.java
  1. … 10 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions() (#10755)

This name change more clearly communicates the semantics of the

feature from a users point of view.

This commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

would have been misleading in the future. To make sure we catch all,

this also updates all variable/method/package names.

    • -9
    • +0
    ./DefaultImmutableVersionConstraint.java
  1. … 70 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -9
    • +0
    ./DefaultImmutableVersionConstraint.java
  1. … 70 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -9
    • +0
    ./DefaultImmutableVersionConstraint.java
  1. … 70 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -9
    • +0
    ./DefaultImmutableVersionConstraint.java
  1. … 70 more files in changeset.
Fix deprecation warning text.

    • -1
    • +1
    ./AbstractExternalModuleDependency.java
  1. … 1 more file in changeset.
Fix deprecation warning text.

    • -1
    • +1
    ./AbstractExternalModuleDependency.java
  1. … 1 more file 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
    • +5
    ./AbstractExternalModuleDependency.java
    • -3
    • +9
    ./DefaultResolvedVersionConstraint.java
  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
    • +5
    ./AbstractExternalModuleDependency.java
    • -3
    • +9
    ./DefaultResolvedVersionConstraint.java
  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
    • +5
    ./AbstractExternalModuleDependency.java
    • -3
    • +9
    ./DefaultResolvedVersionConstraint.java
  1. … 22 more files in changeset.
Cleanup unused code

    • -3
    • +0
    ./DefaultResolvedVersionConstraint.java
Cleanup unused code

    • -3
    • +0
    ./DefaultResolvedVersionConstraint.java
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).

    • -9
    • +8
    ./DefaultImmutableVersionConstraint.java
    • -17
    • +1
    ./DefaultMutableVersionConstraint.java
    • -2
    • +1
    ./DefaultProjectDependencyConstraint.java
    • -3
    • +10
    ./DefaultResolvedVersionConstraint.java
  1. … 73 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).

    • -9
    • +8
    ./DefaultImmutableVersionConstraint.java
    • -17
    • +1
    ./DefaultMutableVersionConstraint.java
    • -2
    • +1
    ./DefaultProjectDependencyConstraint.java
    • -3
    • +10
    ./DefaultResolvedVersionConstraint.java
  1. … 75 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).

    • -9
    • +8
    ./DefaultImmutableVersionConstraint.java
    • -17
    • +1
    ./DefaultMutableVersionConstraint.java
    • -2
    • +1
    ./DefaultProjectDependencyConstraint.java
    • -3
    • +10
    ./DefaultResolvedVersionConstraint.java
  1. … 73 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).

    • -9
    • +8
    ./DefaultImmutableVersionConstraint.java
    • -17
    • +1
    ./DefaultMutableVersionConstraint.java
    • -2
    • +1
    ./DefaultProjectDependencyConstraint.java
    • -3
    • +10
    ./DefaultResolvedVersionConstraint.java
  1. … 73 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).

    • -9
    • +8
    ./DefaultImmutableVersionConstraint.java
    • -17
    • +1
    ./DefaultMutableVersionConstraint.java
    • -2
    • +1
    ./DefaultProjectDependencyConstraint.java
    • -3
    • +10
    ./DefaultResolvedVersionConstraint.java
  1. … 73 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).

    • -9
    • +8
    ./DefaultImmutableVersionConstraint.java
    • -17
    • +1
    ./DefaultMutableVersionConstraint.java
    • -2
    • +1
    ./DefaultProjectDependencyConstraint.java
    • -3
    • +10
    ./DefaultResolvedVersionConstraint.java
  1. … 73 more files in changeset.
Add notInheritConstraints() to module dependency API

    • -18
    • +0
    ./AbstractExternalModuleDependency.java
  1. … 5 more files in changeset.
A version constraint with isForSubgraph() is not requiredOnly()

  1. … 2 more files in changeset.
A version constraint with isForSubgraph() is not requiredOnly()

  1. … 2 more files in changeset.
Add MutableVersionConstraint.notForSubgraph() DSL method

The main use case for this are component metadata rules.

    • -0
    • +5
    ./DefaultMutableVersionConstraint.java
  1. … 3 more files in changeset.
Add MutableVersionConstraint.notForSubgraph() DSL method

The main use case for this are component metadata rules.

    • -0
    • +5
    ./DefaultMutableVersionConstraint.java
  1. … 3 more files in changeset.
Introduce constraint inheritance API

    • -0
    • +18
    ./AbstractExternalModuleDependency.java
  1. … 40 more files in changeset.
Introduce constraint inheritance API

    • -0
    • +18
    ./AbstractExternalModuleDependency.java
  1. … 40 more files in changeset.
Introduce constraint inheritance API

    • -0
    • +18
    ./AbstractExternalModuleDependency.java
  1. … 40 more files in changeset.
Introduce constraint inheritance API

    • -0
    • +18
    ./AbstractExternalModuleDependency.java
  1. … 41 more files in changeset.
Relax constraints inheritance behavior

    • -3
    • +0
    ./AbstractExternalModuleDependency.java
  1. … 1 more file in changeset.
Add `inheritSubgraphConstraints()` API to dependencies

    • -0
    • +21
    ./AbstractExternalModuleDependency.java
  1. … 61 more files in changeset.