ResolutionResultApiIntegrationTest.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

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

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

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

    • -4
    • +0
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 29 more files in changeset.
Report misuse of `getDependenciesForVariant`

    • -0
    • +119
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 1 more file in changeset.
Report misuse of `getDependenciesForVariant`

    • -0
    • +119
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 1 more file in changeset.
Add requested attributes to the resolution result

This is done so that it is possible to find out what

attributes were requested/compatible/missing in variants

based on the consumer attributes, without having to

resort on finding the configuration being resolved.

This is mostly useful in build scans where the plugin

listens to every resolution result, but does not necessarily

know what configuration was resolved to generate this

result.

    • -4
    • +17
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 16 more files in changeset.
Add requested attributes to the resolution result

This is done so that it is possible to find out what

attributes were requested/compatible/missing in variants

based on the consumer attributes, without having to

resort on finding the configuration being resolved.

This is mostly useful in build scans where the plugin

listens to every resolution result, but does not necessarily

know what configuration was resolved to generate this

result.

    • -4
    • +17
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 16 more files in changeset.
Add test about desugaring of dependency attributes

    • -0
    • +28
    ./ResolutionResultApiIntegrationTest.groovy
Add test about desugaring of dependency attributes

    • -0
    • +28
    ./ResolutionResultApiIntegrationTest.groovy
Add tests for resolution result variant API

    • -0
    • +109
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 3 more files in changeset.
Add tests for resolution result variant API

    • -0
    • +109
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix inconsistent serialization state when resolution cache expires

Resolution results are cached, but the cache may expire or entries

in the cache may be evicted, in case there are many configurations

resolved. This has the consequence that the streaming resolution

builder root factory may be called multiple times for the same

configuration, and therefore the file may be read several times

within a build.

This commit fixes a bug with attribute serialization where the state

of the serializer would make the 2d read incorrect.

    • -2
    • +17
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix inconsistent serialization state when resolution cache expires

Resolution results are cached, but the cache may expire or entries

in the cache may be evicted, in case there are many configurations

resolved. This has the consequence that the streaming resolution

builder root factory may be called multiple times for the same

configuration, and therefore the file may be read several times

within a build.

This commit fixes a bug with attribute serialization where the state

of the serializer would make the 2d read incorrect.

    • -2
    • +17
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix inconsistent serialization state when resolution cache expires

Resolution results are cached, but the cache may expire or entries

in the cache may be evicted, in case there are many configurations

resolved. This has the consequence that the streaming resolution

builder root factory may be called multiple times for the same

configuration, and therefore the file may be read several times

within a build.

This commit fixes a bug with attribute serialization where the state

of the serializer would make the 2d read incorrect.

    • -2
    • +17
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 1 more file in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

    • -7
    • +7
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 19 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

    • -7
    • +7
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 19 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

    • -7
    • +7
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 19 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

    • -7
    • +7
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 19 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

    • -7
    • +7
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 19 more files in changeset.
Reshuffle some tests into subpackages

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

package started to grow significantly.

    • -0
    • +406
    ./ResolutionResultApiIntegrationTest.groovy
  1. … 79 more files in changeset.