Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

  1. … 2 more files in changeset.
Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Fixes #11050

Add compatibility layer for SNAPSHOT metadata

Gradle 5.3 to 5.6 have an issue when publishing a Gradle Module Metadata

with a unique snapshot.

This commit enables Gradle 6+ to consume such metadata files without

error.

Fixes #9462

    • -0
    • +10
    ./AbstractMutableModuleComponentResolveMetadata.java
  1. … 3 more files in changeset.
Add compatibility layer for SNAPSHOT metadata

Gradle 5.3 to 5.6 have an issue when publishing a Gradle Module Metadata

with a unique snapshot.

This commit enables Gradle 6+ to consume such metadata files without

error.

    • -0
    • +10
    ./AbstractMutableModuleComponentResolveMetadata.java
  1. … 3 more files in changeset.
Add compatibility layer for SNAPSHOT metadata

Gradle 5.3 to 5.6 have an issue when publishing a Gradle Module Metadata

with a unique snapshot.

This commit enables Gradle 6+ to consume such metadata files without

error.

    • -0
    • +10
    ./AbstractMutableModuleComponentResolveMetadata.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
    ./DefaultComponentVariantIdentifier.java
    • -1
    • +13
    ./maven/DefaultMutableMavenModuleResolveMetadata.java
  1. … 65 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
    ./DefaultComponentVariantIdentifier.java
    • -13
    • +1
    ./maven/DefaultMutableMavenModuleResolveMetadata.java
  1. … 65 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
    ./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
    ./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
    ./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
    ./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
    ./DefaultComponentVariantIdentifier.java
  1. … 12 more files 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
    ./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

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

  1. … 10 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

  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

  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

  1. … 10 more files in changeset.
Re-use immutable capabilities objects in configuration metadata objects

    • -6
    • +5
    ./JavaEcosystemVariantDerivationStrategy.java
Re-use immutable capabilities objects in configuration metadata objects

    • -6
    • +5
    ./JavaEcosystemVariantDerivationStrategy.java
Re-use immutable capabilities objects in configuration metadata objects

    • -1
    • +1
    ./JavaEcosystemVariantDerivationStrategy.java
Re-use immutable capabilities objects in configuration metadata objects

    • -1
    • +1
    ./JavaEcosystemVariantDerivationStrategy.java
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.

    • -7
    • +7
    ./AbstractMutableModuleComponentResolveMetadata.java
    • -3
    • +3
    ./AbstractRealisedModuleResolveMetadataSerializationHelper.java
    • -1
    • +1
    ./AbstractVariantBackedConfigurationMetadata.java
    • -8
    • +8
    ./ConfigurationBoundExternalDependencyMetadata.java
    • -4
    • +4
    ./ForcedDependencyMetadataWrapper.java
    • -1
    • +1
    ./LazyToRealisedModuleComponentResolveMetadataHelper.java
    • -4
    • +4
    ./ModuleDependencyMetadataWrapper.java
  1. … 60 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.

    • -7
    • +7
    ./AbstractMutableModuleComponentResolveMetadata.java
    • -3
    • +3
    ./AbstractRealisedModuleResolveMetadataSerializationHelper.java
    • -1
    • +1
    ./AbstractVariantBackedConfigurationMetadata.java
    • -8
    • +8
    ./ConfigurationBoundExternalDependencyMetadata.java
    • -4
    • +4
    ./ForcedDependencyMetadataWrapper.java
    • -1
    • +1
    ./LazyToRealisedModuleComponentResolveMetadataHelper.java
    • -4
    • +4
    ./ModuleDependencyMetadataWrapper.java
  1. … 60 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.

    • -7
    • +7
    ./AbstractMutableModuleComponentResolveMetadata.java
    • -3
    • +3
    ./AbstractRealisedModuleResolveMetadataSerializationHelper.java
    • -1
    • +1
    ./AbstractVariantBackedConfigurationMetadata.java
    • -8
    • +8
    ./ConfigurationBoundExternalDependencyMetadata.java
    • -4
    • +4
    ./ForcedDependencyMetadataWrapper.java
    • -1
    • +1
    ./LazyToRealisedModuleComponentResolveMetadataHelper.java
    • -4
    • +4
    ./ModuleDependencyMetadataWrapper.java
  1. … 60 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.

    • -7
    • +7
    ./AbstractMutableModuleComponentResolveMetadata.java
    • -3
    • +3
    ./AbstractRealisedModuleResolveMetadataSerializationHelper.java
    • -1
    • +1
    ./AbstractVariantBackedConfigurationMetadata.java
    • -8
    • +8
    ./ConfigurationBoundExternalDependencyMetadata.java
    • -4
    • +4
    ./ForcedDependencyMetadataWrapper.java
    • -1
    • +1
    ./LazyToRealisedModuleComponentResolveMetadataHelper.java
    • -4
    • +4
    ./ModuleDependencyMetadataWrapper.java
  1. … 60 more files in changeset.
Fix application of dependency rules in realized metadata version

The rules for dependencies and dependency constraints were not applied

if the variant itself was added by a rule.

This commit also no longer attempts to apply any rule to the realized

version of 'pure maven configurations'. For Maven, we always use the

derived variants and always use variant matching. Therefore, rules are

never applied to the legacy configurations, but only to the derived

variants.

Follow up to #10368

    • -2
    • +1
    ./ivy/RealisedIvyModuleResolveMetadata.java
    • -14
    • +16
    ./maven/RealisedMavenModuleResolveMetadata.java
  1. … 1 more file in changeset.
Fix application of dependency rules in realized metadata version

The rules for dependencies and dependency constraints were not applied

if the itself variant was added by a rule.

This commit also no longer attempts to apply any rule to the realized

version of 'pure maven configurations'. For Maven, we always use the

derived variants and always use variant matching. Therefore, rules are

never applied to the legacy configurations, but only to the derived

variants.

Follow up to #10368

    • -2
    • +1
    ./ivy/RealisedIvyModuleResolveMetadata.java
    • -14
    • +16
    ./maven/RealisedMavenModuleResolveMetadata.java
  1. … 1 more file in changeset.
Fix application of dependency rules in realized metadata version

The rules for dependencies and dependency constraints were not applied

if the itself variant was added by a rule.

Follow up to #10368

    • -2
    • +1
    ./ivy/RealisedIvyModuleResolveMetadata.java
    • -5
    • +7
    ./maven/RealisedMavenModuleResolveMetadata.java
  1. … 1 more file in changeset.