Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Module test fixture: add 'category' attribute to api/runtime variants

This reflects the default variant attributes of a published

java component.

    • -4
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 13 more files in changeset.
Module test fixture: add 'category' attribute to api/runtime variants

This reflects the default variant attributes of a published

java component.

    • -4
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 13 more files in changeset.
Do not drop variant attributes for 'traditional' maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

    • -4
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
WIP

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -8
    • +8
    ./FeaturesResolveIntegrationTest.groovy
  1. … 46 more files in changeset.
Remove utilisation of *-jars usage values

    • -8
    • +12
    ./FeaturesResolveIntegrationTest.groovy
  1. … 29 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -8
    • +12
    ./FeaturesResolveIntegrationTest.groovy
  1. … 29 more files in changeset.
Remove utilisation of *-jars usage values

    • -8
    • +12
    ./FeaturesResolveIntegrationTest.groovy
  1. … 42 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 55 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -8
    • +12
    ./FeaturesResolveIntegrationTest.groovy
  1. … 48 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 56 more files in changeset.
Remove utilisation of *-jars usage values

    • -10
    • +14
    ./FeaturesResolveIntegrationTest.groovy
  1. … 56 more files in changeset.
Introduce a `JAVA_API_JARS` usage

This commit introduces a new `JAVA_API_JARS` usage, mirror

to the `JAVA_RUNTIME_JARS` usage. This is both for consistency,

and to make sure that the `JAVA_API` and `JAVA_RUNTIME` usages

are limited to cases where the consumer doesn't care, or when

a producer doesn't have a more specific usage to provide.

This is, for example, the case for Java platforms. It's worth

noting than in case a producer mixes both "generic" usages

and "specific" usages, selection is likely to produce unexpected

results, because of disambiguation rules.

The Java disambiguation rule has been simplified and now

supports more cases.

    • -10
    • +10
    ./FeaturesResolveIntegrationTest.groovy
  1. … 37 more files in changeset.
Rename test to remove mention of "optional"

    • -0
    • +191
    ./FeaturesResolveIntegrationTest.groovy
  1. … 1 more file in changeset.