Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -1
    • +16
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -1
    • +16
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -1
    • +16
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -1
    • +16
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -1
    • +16
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -1
    • +16
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

    • -0
    • +33
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 5 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

    • -0
    • +33
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 5 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +4
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +4
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +4
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +4
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +4
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 33 more files in changeset.
Add validation at publication time

This commit introduces validation when generating Gradle

Module Metadata:

- check that there's at least one variant published

- each variant must have at least one attribute

- there shouldn't be duplicate variant names

- each variant must have a different (attributes,capabilities)

combination

Closes #10736

    • -20
    • +27
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 11 more files in changeset.
Add validation at publication time

This commit introduces validation when generating Gradle

Module Metadata:

- check that there's at least one variant published

- each variant must have at least one attribute

- there shouldn't be duplicate variant names

- each variant must have a different (attributes,capabilities)

combination

Closes #10736

    • -20
    • +27
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 11 more files in changeset.
Add validation at publication time

This commit introduces validation when generating Gradle

Module Metadata:

- check that there's at least one variant published

- each variant must have at least one attribute

- there shouldn't be duplicate variant names

- each variant must have a different (attributes,capabilities)

combination

Closes #10736

    • -20
    • +27
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 11 more files in changeset.
Preserve strictly when publishing resolved version

* When the initial version declaration uses `strictly`, then the

resolved version will also be defined as `strictly`.

Fixes #10533

    • -6
    • +164
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Preserve strictly when publishing resolved version

* WHen the initial version declaration uses `strictly`, then the

resolved version will also be defined as `strictly`.

Fixes #10533

    • -6
    • +164
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Preserve strictly when publishing resolved version

* When the initial version declaration uses `strictly`, then the

resolved version will also be defined as `strictly`.

Fixes #10533

    • -6
    • +164
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Fix skipping of empty versions

* When no version is specified, the entire `version` block is to be

skipped. This was not the case due to a type mismatch.

* However if a resolved version is to be written, then the block should

never be skipped.

    • -3
    • +0
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file in changeset.
Fix skipping of empty versions

* When no version is specified, the entire `version` block is to be

skipped. This was not the case due to a type mismatch.

* However if a resolved version is to be written, then the block should

never be skipped.

    • -3
    • +0
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 1 more file 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).

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 77 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).

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 79 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).

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 77 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).

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 77 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).

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 77 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).

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 77 more files in changeset.
Add test coverage for artifact selectors in GMM

    • -1
    • +11
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 5 more files in changeset.
Add test coverage for artifact selectors in GMM

    • -1
    • +11
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 8 more files in changeset.
Implement subgraph constraints support in resolution engine

    • -2
    • +2
    ./publish/internal/ModuleMetadataFileGeneratorTest.groovy
  1. … 7 more files in changeset.