Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixes for lastest 2.0 snapshot

    • -1
    • +25
    ./fixtures/AbstractMultiTestRunner.java
  1. … 1 more file in changeset.
Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

  1. … 39 more files in changeset.
Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

  1. … 24 more files in changeset.
Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

  1. … 24 more files in changeset.
Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

  1. … 24 more files in changeset.
Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

  1. … 24 more files in changeset.
Introduce a factory service to create instances of `TaskDependency`, to allow the implementations to be contextualized and to use types that aren't part of the (internal) core API.

Use this factory in `DefaultConfigurableFileCollection`.

  1. … 39 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Tweak comment about support for JDK12

Tweak comment about support for JDK12

Do not use deprecated configurations in tests

  1. … 5 more files in changeset.
Do not use deprecated configurations in tests

  1. … 5 more files in changeset.
Do not use deprecated configurations in tests

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

    • -6
    • +0
    ./fixtures/FeaturePreviewsFixture.groovy
    • -8
    • +2
    ./fixtures/GradleMetadataResolveRunner.groovy
  1. … 94 more files in changeset.
Adjust multi-line strings to work with both Groovy and JDK13 stripIndent methods

  1. … 8 more files in changeset.
Adjust multi-line strings to work with both Groovy and JDK13 stripIndent methods

  1. … 13 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.

    • -6
    • +0
    ./fixtures/FeaturePreviewsFixture.groovy
    • -8
    • +2
    ./fixtures/GradleMetadataResolveRunner.groovy
  1. … 31 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.

    • -6
    • +0
    ./fixtures/FeaturePreviewsFixture.groovy
    • -8
    • +2
    ./fixtures/GradleMetadataResolveRunner.groovy
  1. … 31 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.

    • -6
    • +0
    ./fixtures/FeaturePreviewsFixture.groovy
    • -8
    • +2
    ./fixtures/GradleMetadataResolveRunner.groovy
  1. … 31 more files in changeset.
Restrict support for JDK13 to versions after 5.6

  1. … 1 more file in changeset.
Remove deprecated `DefaultFileCollectionFactory` constructor

  1. … 2 more files in changeset.
Remove deprecated `DefaultFileCollectionFactory` constructor

  1. … 2 more files in changeset.
Remove deprecated `DefaultFileCollectionFactory` constructor

  1. … 2 more files in changeset.
Remove deprecated `DefaultFileCollectionFactory` constructor

  1. … 2 more files in changeset.
Use stream for creating classpath manifest

Use stream for creating classpath manifest