DependencyHandlerApiResolveIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Reshuffle some tests into subpackages

This is just a refactoring of tests, to make it clearer: the base

package started to grow significantly.

    • -171
    • +0
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 79 more files in changeset.
Use built-in version number from Groovy-all JAR

Instead of trying (and failing) to reproduce the same version number in different places.

    • -3
    • +13
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Revert unnecessary changes

Since we reverted to using groovy-all.jar, there is no need for these changes anymore.

    • -7
    • +7
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 11 more files in changeset.
Revert back to using a groovy-all.jar built by ourselves

See https://github.com/gradle/gradle-groovy-all

    • -7
    • +8
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Fix DependencyHandlerApiResolveIntegrationTest

    • -6
    • +6
    ./DependencyHandlerApiResolveIntegrationTest.groovy
Change test to use new output fixture

    • -1
    • +1
    ./DependencyHandlerApiResolveIntegrationTest.groovy
Run tests that are now relevant (#1875)

* Run tests that are now relevant

* Fix formatting and imports

* Undo unintentional formattings

* Undo unintentional formattings

* Clarify test

    • -2
    • +0
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Temporarily mark some failing specs as @MustFixForV4

    • -0
    • +2
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 15 more files in changeset.
Use a specific artifact identifier for files added for `gradleApi()`, `gradleTestKit()` and `localGroovy()` dependencies, to give some clue as to where these files came from.

    • -15
    • +45
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 14 more files in changeset.
Close jar file after inspecting class entries

    • -5
    • +8
    ./DependencyHandlerApiResolveIntegrationTest.groovy
Renamed `GradleExecuter.requireGradleHome` -> `requireGradleDistribution`

    • -1
    • +1
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 29 more files in changeset.
Usage of cached, fat TestKit JAR requires explicit dependency declaration

- The use of fatGradleApi() and fatGradleTestKit() is currently not multi-process safe.

- Decouple use to allow an easier migration path until the implementation provides support for progress logging and concurrent/multi-process access.

- Fixes cross-version tests that fork concurrent JVMs to run GradleRunner test cases.

+review REVIEW-5867

    • -1
    • +0
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 7 more files in changeset.
Introduce installation beacon and refactor representation of Gradle installation

- Installation discovery by finding JAR in lib directory

- Minor improvements

+review REVIEW-5867

    • -3
    • +3
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 47 more files in changeset.
Create a fat/shaded TestKit JAR to avoid convoluting the functional test runtime classpath with Gradle core classes and external libraries.

- Classes from the TestKit and Tooling API module keep their original package and have not been shaded.

- An other Gradle core classes have been shaded with "org.gradle.jarjar".

- Classes from external libraries have been shaded with "org.gradle.jarjar".

- The method DependencyHandler.gradleTestKit() returns a single, self-contained JAR.

- As a result, user will not have to deal with version conflicts for external libraries e.g. Google Guava.

- Users will not able to reference Gradle core classes by their original package name.

+review REVIEW-5653

    • -5
    • +7
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 4 more files in changeset.
This test doesn't need a daemon, it needs to run against a Gradle distribution.

    • -2
    • +4
    ./DependencyHandlerApiResolveIntegrationTest.groovy
Fix test after package name change.

+review REVIEW-5533

    • -1
    • +1
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 1 more file in changeset.
Rename 'org.gradle.testkit.functional' to 'org.gradle.testkit.runner'.

There will likely be other parts to the testkit, that are used for functional testing (e.g. repo test doubles), and we don’t want to jam them all into the same package.

+review REVIEW-5533

    • -2
    • +2
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 51 more files in changeset.
Settle on test-kit module name for now. The term "functional" doesn't add much at this stage.

+review REVIEW-5533

    • -1
    • +1
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 42 more files in changeset.
Verify that test-kit dependency is required to compile classes referencing its classes.

+review REVIEW-5533

    • -19
    • +54
    ./DependencyHandlerApiResolveIntegrationTest.groovy
Based on Daz's feedback renamed testKit() method to gradleTestKit() to be more specific.

+review REVIEW-5533

    • -2
    • +2
    ./DependencyHandlerApiResolveIntegrationTest.groovy
  1. … 8 more files in changeset.
Make sure that gradleAPI() dependencies don't include test-kit dependency.

+review REVIEW-5533

    • -0
    • +89
    ./DependencyHandlerApiResolveIntegrationTest.groovy