Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add equality check in case update() is called twice for the same input

Add equality check in case update() is called twice for the same input

Add equality check in case update() is called twice for the same input

Add equality check in case update() is called twice for the same input

Fix code comment

Fix code comment

Fix code comment

Fix code comment

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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 4 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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 4 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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 4 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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 4 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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 5 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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 2 more files in changeset.
Remove unused imports

  1. … 1 more file in changeset.
Remove unused imports

  1. … 1 more file in changeset.
Remove unused imports

  1. … 1 more file in changeset.
Remove unused imports

  1. … 1 more file in changeset.
Use the first found dependency artifact for override metadata

Later in the resolution, we already combine all artifacts defined

as 'dependency artifacts' on incoming edges.

If a component does not have metadata, we need at least information

about one artifact early when we look for an artifact (instead of a

metadata file).

    • -1
    • +0
    ./selectors/SelectorStateResolverResults.java
  1. … 6 more files in changeset.
Use the first found dependency artifact for override metadata

Later in the resolution, we already combine all artifacts defined

as 'dependency artifacts' on incoming edges.

If a component does not have metadata, we need at least information

about one artifact early when we look for an artifact (instead of a

metadata file).

    • -1
    • +0
    ./selectors/SelectorStateResolverResults.java
  1. … 6 more files in changeset.
Use the first found dependency artifact for override metadata

Later in the resolution, we already combine all artifacts defined

as 'dependency artifacts' on incoming edges.

If a component does not have metadata, we need at least information

about one artifact early when we look for an artifact (instead of a

metadata file).

    • -1
    • +0
    ./selectors/SelectorStateResolverResults.java
  1. … 6 more files in changeset.
Use the first found dependency artifact for override metadata

Later in the resolution, we already combine all artifacts defined

as 'dependency artifacts' on incoming edges.

If a component does not have metadata, we need at least information

about one artifact early when we look for an artifact (instead of a

metadata file).

    • -1
    • +0
    ./selectors/SelectorStateResolverResults.java
  1. … 6 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.

    • -0
    • +3
    ./selectors/ResolvableSelectorState.java
  1. … 2 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.

    • -0
    • +3
    ./selectors/ResolvableSelectorState.java
  1. … 2 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.

    • -0
    • +3
    ./selectors/ResolvableSelectorState.java
  1. … 2 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.

    • -0
    • +3
    ./selectors/ResolvableSelectorState.java
  1. … 2 more files in changeset.
Use the dependency artifacts of all selectors for override metadata

Later in the resolution, we already combine all artifacts defined

as 'dependency artifacts' on incoming edges.

If a component does not have metadata, we also need to consider all

this information early when we look for an artifact (instead of a

metadata file).

    • -1
    • +0
    ./selectors/SelectorStateResolverResults.java
  1. … 6 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.

    • -0
    • +5
    ./selectors/ResolvableSelectorState.java
  1. … 2 more files in changeset.
Remove private 'firstSeenDependency' field

This is just a shortcut to a final filed in 'dependencyState'.

Sometimes it was used and sometimes 'dependencyState.getDepenedency()'

was used which is always the same value.

This makes this complex code a bit easier to comprehend.

Remove private 'firstSeenDependency' field

This is just a shortcut to a final filed in 'dependencyState'.

Sometimes it was used and sometimes 'dependencyState.getDepenedency()'

was used which is always the same value.

This makes this complex code a bit easier to comprehend.