MixedDependencyLockingIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add @ToBeFixedForInstantExecution to MixedDependencyLockingIntegrationTest

because the :dependencyInsight task has a Configuration field

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +3
    ./MixedDependencyLockingIntegrationTest.groovy
Add test coverage for per project lockfile

This is done by making sure most tests cover both the existing file

format and the upcoming file format.

Issue #11881

    • -4
    • +4
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 14 more files in changeset.
Rename test methods and fixtures

Given that a new format will be introduced for dependency lock files,

the existing methods have legacy in their name for clear identification.

    • -6
    • +6
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 11 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -2
    • +2
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +2
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 93 more files in changeset.
Do not permit stack-traces to be emitted by integration tests

    • -4
    • +0
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 1 more file in changeset.
Enable improved POM support by default

This commit makes the experimental flag `IMPROVED_POM_SUPPORT` the default.

The flag is still there for backwards compatibility but has effectively no

impact. As a consequence, the behavior of improved POM support is now the

default, which implies that:

- Maven dependencies packaged as `pom` or `jar` now have derived variants

(`compile` and `runtime`) and we properly choose between the variants based

on the consumer attributes

- platform dependencies using the `platform` and `enforcedPlatform` keywords

are enabled

Enabling improved POM support by default is a **breaking change**: there's

a risk that resolved dependencies is different, in particular because we

will now only include the `compile` dependencies of a POM file whenever the

consumer asks for the API variant. There are also some changes in the

dependency insight reports due to the use of attribute based matching instead

of configuration selection.

Last but not least, this commit is likely to introduce a small performance

regression due to attribute based selection.

    • -0
    • +4
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 50 more files in changeset.
Minor error message improvement

    • -2
    • +2
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 3 more files in changeset.
Improve dependency locking test coverage

Issue #4904

    • -0
    • +172
    ./MixedDependencyLockingIntegrationTest.groovy
  1. … 4 more files in changeset.