Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Backport test fixture improvements from 6.0 branch

  1. … 2 more files in changeset.
Backport test fixture improvements from 6.0 branch

  1. … 2 more files in changeset.
Backport test fixture improvements from 6.0 branch

  1. … 2 more files in changeset.
Do not expect an exact number of HEAD requests

This seems to be dependent on timing. If one request starts after

another did already finish, it can take the result from cache.

  1. … 1 more file in changeset.
Do not expect an exact number of HEAD requests

This seems to be dependent on timing. If one request starts after

another did already finish, it can take the result from cache.

  1. … 1 more file in changeset.
Do not expect an exact number of HEAD requests

This seems to be dependent on timing. If one request starts after

another did already finish, it can take the result from cache.

  1. … 1 more file in changeset.
Do not expect an exact number of HEAD requests

This seems to be dependent on timing. If one request starts after

another did already finish, it can take the result from cache.

  1. … 1 more file in changeset.
Add test for classifier selection behavior if provider publishes GMM

  1. … 2 more files in changeset.
Extend test fixture for testing artifact selectors in GMM

  1. … 9 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 31 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 32 more files in changeset.
Extend test fixtures to test with artifact selectors

  1. … 7 more files in changeset.
Add test coverage for artifact selectors

  1. … 10 more files in changeset.
Extend test fixtures to test with artifact selectors

  1. … 7 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -52
    • +27
    ./publish/ModuleVersionSpec.groovy
  1. … 95 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -52
    • +27
    ./publish/ModuleVersionSpec.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -52
    • +27
    ./publish/ModuleVersionSpec.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -52
    • +27
    ./publish/ModuleVersionSpec.groovy
  1. … 32 more files in changeset.
Add integration tests for module metadata validation

  1. … 9 more files in changeset.
Add integration tests for module metadata validation

  1. … 9 more files in changeset.
Add integration tests for module metadata validation

  1. … 9 more files in changeset.
Add integration tests for module metadata validation

  1. … 9 more files in changeset.
Unify 'VariantSpec' and 'VariantMetadataSpec'

These data structures in the test fixtures were very similar which

leads to duplication that needs to be maintained and changed in

parallel each time we extend/modify the expressiveness of variant

metadata.

    • -22
    • +13
    ./publish/ModuleVersionSpec.groovy
  1. … 5 more files in changeset.
Unify 'VariantSpec' and 'VariantMetadataSpec'

These data structures in the test fixtures were very similar which

leads to duplication that needs to be maintained and changed in

parallel each time we extend/modify the expressiveness of variant

metadata.

    • -22
    • +13
    ./publish/ModuleVersionSpec.groovy
  1. … 5 more files in changeset.
Implement classifier to variant mapping

This commit implements a strategy to disambiguate

variants whenever the consumer uses a classifier

in the dependency descriptor. This can be the case

if a Maven library depends on a Gradle library published

with Gradle module metadata, or even if a Gradle

library depends on another Gradle library but makes

use of a classifier (when it should really be using an

attribute).

  1. … 8 more files in changeset.
Implement classifier to variant mapping

This commit implements a strategy to disambiguate

variants whenever the consumer uses a classifier

in the dependency descriptor. This can be the case

if a Maven library depends on a Gradle library published

with Gradle module metadata, or even if a Gradle

library depends on another Gradle library but makes

use of a classifier (when it should really be using an

attribute).

  1. … 8 more files in changeset.
Implement enforced platforms via variants instead of component metadata rules

This commit replaces the component metadat rules implementation with

proper variant based matching. It introduces a new attribute, the component

category, which can currently be either a library or a platform. By default,

components are assumed to be libraries.

  1. … 14 more files in changeset.