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+

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

Fixes #9462

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

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

  1. … 4 more files in changeset.
GradlePomModuleDescriptorParser: resolve GAV after configuring parent in case POM inherits portions for name/group/version from the parent

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

    • -0
    • +45
    ./ivyresolve/parser/GradlePomModuleDescriptorParserTest.groovy
  1. … 1 more file in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -1
    • +1
    ./modulecache/artifacts/DefaultModuleArtifactCacheTest.groovy
  1. … 8 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -1
    • +1
    ./modulecache/artifacts/DefaultModuleArtifactCacheTest.groovy
  1. … 8 more files in changeset.
Update module cache content

Reference to file are now relative to the root of the module cache

instead of being absolute.

This should allow moving the full module cache around to be reused with

a different root path.

    • -1
    • +1
    ./modulecache/artifacts/DefaultModuleArtifactCacheTest.groovy
  1. … 6 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -1
    • +1
    ./modulecache/artifacts/DefaultModuleArtifactCacheTest.groovy
  1. … 8 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.

  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.

  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.

  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.

  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.

  1. … 6 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).

    • -6
    • +0
    ./resolveengine/AbstractConflictResolverTest.groovy
  1. … 8 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
    • +0
    ./resolveengine/AbstractConflictResolverTest.groovy
  1. … 8 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
    • +0
    ./resolveengine/AbstractConflictResolverTest.groovy
  1. … 8 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
    • +0
    ./resolveengine/AbstractConflictResolverTest.groovy
  1. … 8 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./projectmodule/ProjectDependencyResolverTest.groovy
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./projectmodule/ProjectDependencyResolverTest.groovy
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./projectmodule/ProjectDependencyResolverTest.groovy
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./projectmodule/ProjectDependencyResolverTest.groovy
  1. … 3 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.

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

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

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

  1. … 3 more files in changeset.