Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

    • -2
    • +11
    ./MavenUniqueSnapshotExternalResourceArtifactResolver.java
  1. … 1 more file in changeset.
Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

    • -2
    • +11
    ./MavenUniqueSnapshotExternalResourceArtifactResolver.java
  1. … 1 more file in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

  1. … 9 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

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

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

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

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

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

Fixes #10916

    • -0
    • +5
    ./MavenUniqueSnapshotExternalResourceArtifactResolver.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

    • -0
    • +5
    ./MavenUniqueSnapshotExternalResourceArtifactResolver.java
  1. … 7 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
    ./AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./DirectDependencyMetadataAdapter.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
    ./AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./DirectDependencyMetadataAdapter.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
    ./AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./DirectDependencyMetadataAdapter.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
    ./AbstractDependenciesMetadataAdapter.java
    • -1
    • +1
    ./DependencyConstraintsMetadataAdapter.java
    • -2
    • +2
    ./DirectDependenciesMetadataAdapter.java
    • -6
    • +6
    ./DirectDependencyMetadataAdapter.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
    ./DirectDependencyMetadataAdapter.java
  1. … 30 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -4
    • +4
    ./DirectDependencyMetadataAdapter.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
    ./DirectDependencyMetadataAdapter.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
    ./DirectDependencyMetadataAdapter.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
    ./DirectDependencyMetadataAdapter.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
    ./DirectDependencyMetadataAdapter.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
    ./DirectDependencyMetadataAdapter.java
  1. … 76 more files in changeset.