Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./resolver/ExternalResourceResolverDescriptorParseContext.java
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./resolver/ExternalResourceResolverDescriptorParseContext.java
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./resolver/ExternalResourceResolverDescriptorParseContext.java
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./resolver/ExternalResourceResolverDescriptorParseContext.java
  1. … 3 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -1
    • +1
    ./resolver/ExternalResourceResolverDescriptorParseContext.java
  1. … 3 more files in changeset.
Revert "Revert "Merge branch 'release'""

This reverts commit 67b8bb8f18f854f45a2f5ec52cc9c8a25981e2f2.

This restores the merge attempt from earlier.

    • -1
    • +1
    ./metadata/DefaultGradleModuleMetadataSource.java
    • -7
    • +7
    ./metadata/IvyMutableModuleMetadataFactory.java
    • -3
    • +4
    ./metadata/MavenMutableModuleMetadataFactory.java
    • -1
    • +2
    ./metadata/MutableModuleMetadataFactory.java
  1. … 63 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.

    • -1
    • +1
    ./metadata/DefaultGradleModuleMetadataSource.java
    • -7
    • +7
    ./metadata/IvyMutableModuleMetadataFactory.java
    • -4
    • +3
    ./metadata/MavenMutableModuleMetadataFactory.java
    • -2
    • +1
    ./metadata/MutableModuleMetadataFactory.java
  1. … 63 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
    • +1
    ./metadata/DefaultGradleModuleMetadataSource.java
    • -7
    • +7
    ./metadata/IvyMutableModuleMetadataFactory.java
    • -3
    • +4
    ./metadata/MavenMutableModuleMetadataFactory.java
    • -1
    • +2
    ./metadata/MutableModuleMetadataFactory.java
  1. … 13 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
    • +1
    ./metadata/DefaultGradleModuleMetadataSource.java
    • -7
    • +7
    ./metadata/IvyMutableModuleMetadataFactory.java
    • -3
    • +4
    ./metadata/MavenMutableModuleMetadataFactory.java
    • -1
    • +2
    ./metadata/MutableModuleMetadataFactory.java
  1. … 13 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. … 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

    • -2
    • +45
    ./DefaultMavenArtifactRepository.java
    • -2
    • +2
    ./metadata/RedirectingGradleMetadataModuleMetadataSource.java
  1. … 9 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

    • -2
    • +45
    ./DefaultMavenArtifactRepository.java
    • -2
    • +2
    ./metadata/RedirectingGradleMetadataModuleMetadataSource.java
    • -0
    • +5
    ./resolver/MavenUniqueSnapshotExternalResourceArtifactResolver.java
  1. … 5 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

    • -2
    • +45
    ./DefaultMavenArtifactRepository.java
    • -2
    • +2
    ./metadata/RedirectingGradleMetadataModuleMetadataSource.java
    • -0
    • +5
    ./resolver/MavenUniqueSnapshotExternalResourceArtifactResolver.java
  1. … 5 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

    • -2
    • +45
    ./DefaultMavenArtifactRepository.java
    • -2
    • +2
    ./metadata/RedirectingGradleMetadataModuleMetadataSource.java
  1. … 9 more files in changeset.
Add error message in case GMM doesn't declare variants

This commit validates that published Gradle Module Metadata

declares at least one variant when resolved. This is the

counterpart to validation at publication time, but this time

when resolving, in case a user/plugin generates module metadata

in a non-Gradle compatible way.

    • -0
    • +10
    ./metadata/DefaultGradleModuleMetadataSource.java
  1. … 6 more files in changeset.
Add error message in case GMM doesn't declare variants

This commit validates that published Gradle Module Metadata

declares at least one variant when resolved. This is the

counterpart to validation at publication time, but this time

when resolving, in case a user/plugin generates module metadata

in a non-Gradle compatible way.

    • -0
    • +10
    ./metadata/DefaultGradleModuleMetadataSource.java
  1. … 6 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.

    • -2
    • +2
    ./resolver/AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./resolver/DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./resolver/DirectDependencyMetadataAdapter.java
    • -7
    • +7
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 66 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.

    • -2
    • +2
    ./resolver/AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./resolver/DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./resolver/DirectDependencyMetadataAdapter.java
    • -7
    • +7
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 66 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.

    • -2
    • +2
    ./resolver/AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./resolver/DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./resolver/DirectDependencyMetadataAdapter.java
    • -7
    • +7
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 66 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.

    • -2
    • +2
    ./resolver/AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./resolver/DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./resolver/DirectDependencyMetadataAdapter.java
    • -7
    • +7
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 66 more files in changeset.
Support adding variants and files in component metadata rules (#10368)

Support adding variants and files in component metadata rules

  1. … 1 more file in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 30 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 30 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 30 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 30 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 30 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 29 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 78 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 76 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -4
    • +4
    ./resolver/DirectDependencyMetadataAdapter.java
    • -2
    • +2
    ./resolver/DirectDependencyMetadataImpl.java
  1. … 76 more files in changeset.