ClasspathDependenciesAttributesIntegrationTest.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
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 95 more files in changeset.
wip - fix more tests

    • -1
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 46 more files in changeset.
wip - fix more tests

    • -1
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 45 more files in changeset.
wip - fix more tests

    • -1
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 46 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.

    • -2
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.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.

    • -2
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.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.

    • -2
    • +0
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 32 more files in changeset.
Fix for changes to singleton.

    • -2
    • +1
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
Replace most usages of `NamedObjectInstantiator.INSTANCE` with injection of a global service instead. This allows the instantiator to be contextualized, for example to handle caching of the generated types.

    • -2
    • +1
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 27 more files in changeset.
Replace most usages of `NamedObjectInstantiator.INSTANCE` with injection of a global service instead. This allows the instantiator to be contextualized, for example to handle caching of the generated types.

    • -2
    • +1
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 27 more files in changeset.
Replace most usages of `NamedObjectInstantiator.INSTANCE` with injection of a global service instead. This allows the instantiator to be contextualized, for example to handle caching of the generated types.

    • -2
    • +1
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 27 more files in changeset.
Add test for plugin resolution and attributes schema

Verifies that the case which did not have the derivation strategy

previously is covered by having the compatibility / disambiguation

rules.

Issue #9424

    • -0
    • +66
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
Add test for plugin resolution and attributes schema

Verifies that the case which did not have the derivation strategy

previously is covered by having the compatibility / disambiguation

rules.

Issue #9424

    • -0
    • +66
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
Add test for plugin resolution and attributes schema

Verifies that the case which did not have the derivation strategy

previously is covered by having the compatibility / disambiguation

rules.

Issue #9424

    • -0
    • +66
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
Add test for plugin resolution and attributes schema

Verifies that the case which did not have the derivation strategy

previously is covered by having the compatibility / disambiguation

rules.

Issue #9424

    • -0
    • +66
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
Make sure build classpath _always_ uses Java derivation

Previously there was a code path where the derivation strategy was not

wired in.

    • -0
    • +73
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 1 more file in changeset.
Make sure build classpath _always_ uses Java derivation

Previously there was a code path where the derivation strategy was not

wired in.

Fixes #9424

    • -0
    • +73
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 1 more file in changeset.
Make sure build classpath _always_ uses Java derivation

Previously there was a code path where the derivation strategy was not

wired in.

Fixes #9424

    • -0
    • +73
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 1 more file in changeset.
Make sure build classpath _always_ uses Java derivation

Previously there was a code path where the derivation strategy was not

wired in.

    • -0
    • +72
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 1 more file in changeset.
Make sure build classpath _always_ uses Java derivation

Previously there was a code path where the derivation strategy was not

wired in.

    • -0
    • +73
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 1 more file in changeset.
Make sure build classpath _always_ uses Java derivation

Previously there was a code path where the derivation strategy was not

wired in.

Fixes #9424

    • -0
    • +73
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 1 more file in changeset.
Use Java variant derivation strategy for scripts

The script classpath is about building a Java classpath and thus uses

now the `JavaEcosystemVariantDerivationStrategy`.

In practice this should have no visible impact, it however makes sure we

are consistent in resolving in a Java context.

Issue #7826

    • -0
    • +130
    ./ClasspathDependenciesAttributesIntegrationTest.groovy
  1. … 5 more files in changeset.