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.

    • -3
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  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.

    • -3
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  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.

    • -3
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  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.

    • -3
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  1. … 7 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.

    • -3
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  1. … 4 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).

    • -6
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  1. … 9 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).

    • -6
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  1. … 9 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).

    • -6
    • +6
    ./model/DefaultComponentOverrideMetadata.java
  1. … 9 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -2
    • +4
    ./model/DefaultComponentOverrideMetadata.java
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -2
    • +4
    ./model/DefaultComponentOverrideMetadata.java
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -2
    • +4
    ./model/DefaultComponentOverrideMetadata.java
  1. … 3 more files in changeset.
Avoid copying an already immutable list

    • -1
    • +1
    ./model/LocalComponentDependencyMetadata.java
Avoid copying an already immutable list

    • -1
    • +1
    ./model/LocalComponentDependencyMetadata.java
Avoid copying an already immutable list

    • -1
    • +1
    ./model/LocalComponentDependencyMetadata.java
Avoid copying an already immutable list

    • -1
    • +1
    ./model/LocalComponentDependencyMetadata.java
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).

    • -2
    • +2
    ./model/DefaultComponentOverrideMetadata.java
  1. … 9 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -2
    • +4
    ./model/DefaultComponentOverrideMetadata.java
  1. … 3 more files in changeset.
Revert "Revert "Merge branch 'release'""

This reverts commit 67b8bb8f18f854f45a2f5ec52cc9c8a25981e2f2.

This restores the merge attempt from earlier.

    • -0
    • +46
    ./external/model/DefaultComponentVariantIdentifier.java
    • -1
    • +13
    ./external/model/maven/DefaultMutableMavenModuleResolveMetadata.java
    • -1
    • +1
    ./model/AttributeConfigurationSelector.java
  1. … 64 more files in changeset.
Revert "Merge branch 'release'"

This reverts commit c7fdc455dcb9a8016af0ae9bc8b4c43fde1e2d06, reversing

changes made to 9f70d52b74dbc8c71381781b6c155474031b3cf8.

The changes need a wrapper as there are API changes. Reverting for now.

    • -46
    • +0
    ./external/model/DefaultComponentVariantIdentifier.java
    • -13
    • +1
    ./external/model/maven/DefaultMutableMavenModuleResolveMetadata.java
    • -1
    • +1
    ./model/AttributeConfigurationSelector.java
  1. … 64 more files in changeset.
Support variant selection in capability conflict resolution (#10973)

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

    • -0
    • +46
    ./external/model/DefaultComponentVariantIdentifier.java
  1. … 13 more files in changeset.
Changes in Gradle Module Metadata loading

We no longer define any configurations, like default or the maven ones.

In the past, we still had these defined which allowed partial legacy

selection. But it made no sense since all these configurations would not

have any dependencies for example.

Fixes #10980

    • -1
    • +13
    ./external/model/maven/DefaultMutableMavenModuleResolveMetadata.java
  1. … 16 more files in changeset.
Changes in Gradle Module Metadata generation

We no longer define any configurations, like default or the maven ones.

In the past, we still had these defined which allowed partial legacy

selection. But it made no sense since all these configurations would not

have any dependencies for example.

    • -1
    • +13
    ./external/model/maven/DefaultMutableMavenModuleResolveMetadata.java
  1. … 16 more files in changeset.
Support variant selection in capability conflict resolution

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

    • -0
    • +46
    ./external/model/DefaultComponentVariantIdentifier.java
  1. … 13 more files in changeset.
Support variant selection in capability conflict resolution

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

    • -0
    • +46
    ./external/model/DefaultComponentVariantIdentifier.java
  1. … 12 more files in changeset.
Fix AttributeConfigurationSelector to return the filtered result 2/2

Same as 3255f1d for different code path.

    • -1
    • +1
    ./model/AttributeConfigurationSelector.java
  1. … 1 more file in changeset.
Fix AttributeConfigurationSelector to return the filtered result 2/2

Same as 3255f1d for different code path.

    • -1
    • +1
    ./model/AttributeConfigurationSelector.java
  1. … 1 more file in changeset.
Fix realization of Maven metadata

The fix to handle SNAPSHOT dependencies correctly with Gradle

Module Metadata exposed a couple of failures in the "force

realize" cases, which correspond to the cases where metadata

has to be realized pre-emptively (using cached metadata rules

for example).

    • -1
    • +18
    ./external/model/AbstractRealisedModuleResolveMetadataSerializationHelper.java
  1. … 1 more file in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

    • -3
    • +31
    ./external/model/UrlBackedArtifactMetadata.java
  1. … 7 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

    • -3
    • +31
    ./external/model/UrlBackedArtifactMetadata.java
  1. … 7 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -4
    • +29
    ./external/model/UrlBackedArtifactMetadata.java
  1. … 10 more files in changeset.