FileDependencyResolveIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let dependency-management tests not use deprecated configurations

    • -1
    • +1
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -1
    • +1
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -1
    • +1
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Let dependency-management tests not use deprecated configurations

    • -1
    • +1
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 27 more files in changeset.
Move some more direct usages of `DefaultConfigurableFileCollection` instances to instead delegate to `FileCollectionFactory`.

    • -6
    • +4
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 12 more files in changeset.
Move some more direct usages of `DefaultConfigurableFileCollection` instances to instead delegate to `FileCollectionFactory`.

    • -6
    • +4
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 12 more files in changeset.
ResolveTestFixture actually builds artifacts when requested

    • -5
    • +0
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 2 more files in changeset.
Review and improve tests that require exact ordering of tasks

    • -4
    • +4
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 23 more files in changeset.
Test that file collection is listed once per resolve

This test currently fails. File collection is listed once to prepare artifacts

in parallel, and again to visit files.

    • -0
    • +30
    ./FileDependencyResolveIntegrationTest.groovy
Removed some duplicate logic for calculating the files/artifacts for a configuration and calculating the build dependencies for a configuration, so that the results are more often the same. This addresses 2 issues:

- The artifacts of the root configuration were not built when there was a dependency cycle that included the root configuration. These artifacts were included in the result (correct) but their build dependencies were not being included in the configuration's build dependencies (not correct).

- The files dependencies of a configuration reachable only via non-transitive dependencies were built (not correct) even though they are not included in the result (correct).

Added more test coverage for these and similar cases.

    • -0
    • +41
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 15 more files in changeset.
Added some test coverage for using `FileCollections` as dependencies.

    • -0
    • +166
    ./FileDependencyResolveIntegrationTest.groovy
  1. … 2 more files in changeset.