ForcedModulesIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Do not emit deprecation warning for deprecated 'force'"

This reverts commit 1db54192db6ef9af5c2fd6b227004eed9a27c07f.

  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

  1. … 10 more files in changeset.
Fix deprecation warning text.

  1. … 1 more file in changeset.
Fix deprecation warning text.

  1. … 1 more file in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 23 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 18 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 23 more files in changeset.
Do not sort selectors when a force is present

Otherwise the sorting was breaking the "first force wins" behaviour.

    • -3
    • +44
    ./ForcedModulesIntegrationTest.groovy
  1. … 1 more file in changeset.
Do not sort selectors when a force is present

Otherwise the sorting was breaking the "first force wins" behaviour.

    • -3
    • +44
    ./ForcedModulesIntegrationTest.groovy
  1. … 1 more file in changeset.
Let dependency-management tests not use deprecated configurations

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

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

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

    • -31
    • +31
    ./ForcedModulesIntegrationTest.groovy
  1. … 27 more files in changeset.
Implement variant derivation strategy

This commit changes how Maven metadata is derived into variants. Now we will

only derive variants if the Java plugin is applied (the "base Java" plugin).

This is implemented via a variant derivation strategy, and allows fixing

the problem that a native component is unlikely to find sense in the derivation

of Java variants. This fixes a bug where the native plugins wouldn't be able

to consume native libraries published on Maven repositories, without Gradle

metadata.

  1. … 43 more files in changeset.
Tidy up variant-names in integration tests

Instead of inlining the expected variant name in the module coordinates,

use `ResolveTestFixture.expectDefaultConfiguration(variant)`.

  1. … 8 more files 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.

  1. … 50 more files in changeset.
Fix "forced" flag being sometimes ignored

If the first direct dependency we see for a specific module version (g,a,v) has forced=false, then

if another first level dependency (g,a,v) with forced=true is added later, we ignore the fact that

the second one has forced=true. This case was lost during refactorings, due to insufficient test

coverage.

Fixes #5364

    • -0
    • +48
    ./ForcedModulesIntegrationTest.groovy
  1. … 2 more files in changeset.
Add test for force transtive dependency version

    • -0
    • +29
    ./ForcedModulesIntegrationTest.groovy
Use doLast instead of left shift operator

Made this change in preparation for deprecating the left shift operator.

+review REVIEW-6236

    • -19
    • +31
    ./ForcedModulesIntegrationTest.groovy
  1. … 163 more files in changeset.
Rename `o.g.i.c.model.*{MetaData => Metadata}`

  1. … 162 more files in changeset.
Renamed subprojects/core-impl to subprojects/dependency-management.

    • -0
    • +317
    ./ForcedModulesIntegrationTest.groovy
  1. … 1384 more files in changeset.