JavaPlatformResolveIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Adjust tests and samples to new metadata sources defaults

    • -3
    • +3
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 95 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -3
    • +3
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -3
    • +3
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -3
    • +3
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 29 more files in changeset.
WIP

    • -15
    • +9
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

    • -15
    • +8
    ./JavaPlatformResolveIntegrationTest.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.

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

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

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

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

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

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

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

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

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

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

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

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

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

    • -8
    • +16
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 56 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

    • -1
    • +63
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

    • -1
    • +63
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

    • -1
    • +63
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix selection of target configuration with Ivy+constraints

This commit fixes an edge case when a dependency doesn't

use variant awareness, but rather an explicit target

configuration. In particular in the case of Ivy, the fact

of adding a constraint made the build fail with an error

stating that no matching configuration could be selected,

with the list of configurations and their attributes, but

no required attribute.

This case happened when the target module didn't provide

a "default" configuration.

Now we avoid selecting a configuration for constraint edges,

unless they are well known cases (virtual platforms). This

should have a positive impact on performance too.

    • -1
    • +63
    ./JavaPlatformResolveIntegrationTest.groovy
  1. … 4 more files in changeset.