Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add missing hashCode() method

Add missing hashCode() method

Include version constrain comparison in equals() check of dependency

The version constraint was ignored when comparing two dependency

declarations. This can lead to dropping dependency declarations for

the same module with the same required version, even if other version

constraint details differ.

    • -1
    • +3
    ./AbstractExternalModuleDependency.java
  1. … 1 more file in changeset.
Fix equals() of client module

  1. … 1 more file in changeset.
Fix equals() of client module

  1. … 1 more file in changeset.
Fix equals() of client module

Fix equals() of client module

  1. … 1 more file in changeset.
Fix equals() of client module

  1. … 1 more file in changeset.
Remove duplicated 'isKeyEquals' check

    • -1
    • +1
    ./AbstractExternalModuleDependency.java
Remove duplicated 'isKeyEquals' check

    • -1
    • +1
    ./AbstractExternalModuleDependency.java
Remove duplicated 'isKeyEquals' check

    • -1
    • +1
    ./AbstractExternalModuleDependency.java
Remove duplicated 'isKeyEquals' check

    • -1
    • +1
    ./AbstractExternalModuleDependency.java
Simplify test to check that result of resolution can be stable

For this, just reuse the `canShortCircuitSelection` method.

    • -9
    • +1
    ./DefaultResolvedVersionConstraint.java
Simplify test to check that result of resolution can be stable

For this, just reuse the `canShortCircuitSelection` method.

    • -9
    • +1
    ./DefaultResolvedVersionConstraint.java
Fix detection of unstable resolution result

when there are multiple candidates and the selected

version is higher than the non-dynamic selectors

versions.

    • -0
    • +36
    ./DefaultResolvedVersionConstraint.java
  1. … 4 more files in changeset.
Fix detection of unstable resolution result

when there are multiple candidates and the selected

version is higher than the non-dynamic selectors

versions.

    • -0
    • +36
    ./DefaultResolvedVersionConstraint.java
  1. … 4 more files in changeset.
Revert "Do not emit deprecation warning for deprecated 'force'"

This reverts commit 1db54192db6ef9af5c2fd6b227004eed9a27c07f.

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