Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +89
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

    • -0
    • +84
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -56
    • +33
    ./resolve/alignment/ForcingPlatformAlignmentTest.groovy
    • -1
    • +1
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -15
    • +20
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
    • -96
    • +43
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 16 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -17
    • +35
    ./resolve/alignment/ForcingPlatformAlignmentTest.groovy
    • -1
    • +1
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -15
    • +20
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
    • -97
    • +44
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 16 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -56
    • +33
    ./resolve/alignment/ForcingPlatformAlignmentTest.groovy
    • -1
    • +1
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -15
    • +20
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
    • -96
    • +43
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 16 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -17
    • +35
    ./resolve/alignment/ForcingPlatformAlignmentTest.groovy
    • -1
    • +1
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -15
    • +20
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
    • -97
    • +44
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -56
    • +33
    ./resolve/alignment/ForcingPlatformAlignmentTest.groovy
    • -1
    • +1
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -15
    • +20
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
    • -96
    • +43
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 16 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -56
    • +33
    ./resolve/alignment/ForcingPlatformAlignmentTest.groovy
    • -1
    • +1
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -15
    • +20
    ./resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
    • -96
    • +43
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 16 more files in changeset.
Implement strict mode for locking

In strict mode, a locked configuration without a lockfile, empty or not,

is illegal and will cause the build to fail.

    • -0
    • +932
    ./resolve/locking/AbstractLockingIntegrationTest.groovy
    • -870
    • +34
    ./resolve/locking/DependencyLockingIntegrationTest.groovy
    • -0
    • +129
    ./resolve/locking/DependencyLockingStrictModeIntegrationTest.groovy
  1. … 10 more files in changeset.
Implement strict mode for locking

In strict mode, a locked configuration without a lockfile, empty or not,

is illegal and will cause the build to fail.

    • -0
    • +932
    ./resolve/locking/AbstractLockingIntegrationTest.groovy
    • -870
    • +34
    ./resolve/locking/DependencyLockingIntegrationTest.groovy
    • -0
    • +129
    ./resolve/locking/DependencyLockingStrictModeIntegrationTest.groovy
  1. … 10 more files in changeset.
Implement strict mode for locking

In strict mode, a locked configuration without a lockfile, empty or not,

is illegal and will cause the build to fail.

    • -0
    • +932
    ./resolve/locking/AbstractLockingIntegrationTest.groovy
    • -870
    • +34
    ./resolve/locking/DependencyLockingIntegrationTest.groovy
    • -0
    • +129
    ./resolve/locking/DependencyLockingStrictModeIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -12
    • +12
    ./resolve/PublishedRichVersionConstraintsIntegrationTest.groovy
    • -23
    • +23
    ./resolve/RichVersionConstraintsIntegrationTest.groovy
    • -8
    • +8
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -8
    • +8
    ./resolve/locking/DependencyLockingIntegrationTest.groovy
    • -15
    • +15
    ./resolve/rules/DependencyMetadataRulesIntegrationTest.groovy
    • -6
    • +6
    ./resolve/strict/EndorseStrictVersionsIntegrationTest.groovy
    • -19
    • +19
    ./resolve/strict/StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
    • -14
    • +14
    ./resolve/strict/StrictVersionConstraintsIntegrationTest.groovy
    • -7
    • +7
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 1 more file in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -12
    • +12
    ./resolve/PublishedRichVersionConstraintsIntegrationTest.groovy
    • -23
    • +23
    ./resolve/RichVersionConstraintsIntegrationTest.groovy
    • -8
    • +8
    ./resolve/alignment/ForcingUsingStrictlyPlatformAlignmentTest.groovy
    • -8
    • +8
    ./resolve/locking/DependencyLockingIntegrationTest.groovy
    • -15
    • +15
    ./resolve/rules/DependencyMetadataRulesIntegrationTest.groovy
    • -6
    • +6
    ./resolve/strict/EndorseStrictVersionsIntegrationTest.groovy
    • -19
    • +19
    ./resolve/strict/StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
    • -14
    • +14
    ./resolve/strict/StrictVersionConstraintsIntegrationTest.groovy
    • -7
    • +7
    ./resolve/strict/StrictVersionsInPlatformCentricDevelopmentIntegrationTest.groovy
  1. … 2 more files in changeset.
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

    • -1
    • +1
    ./resolve/ResolveConfigurationDependenciesBuildOperationIntegrationTest.groovy
    • -1
    • +1
    ./resolve/constraints/DependencyConstraintsIntegrationTest.groovy
  1. … 71 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 10 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 10 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 10 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 10 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

    • -3
    • +47
    ./resolve/CacheResolveIntegrationTest.groovy
  1. … 9 more files in changeset.
Include version constraint comparison in equals() check of dependency (#11001)

The version constraint was ignored when comparing two dependency

declarations. This can lead to dropping dependency declarations for

the same module with the same required version, even if other version

constraint details differ.

    • -0
    • +33
    ./resolve/strict/StrictVersionConstraintsIntegrationTest.groovy
  1. … 1 more file in changeset.
Relax flaky test expectation

    • -3
    • +2
    ./resolve/override/ComponentOverrideMetadataResolveIntegrationTest.groovy
Relax flaky test expectation

    • -3
    • +2
    ./resolve/override/ComponentOverrideMetadataResolveIntegrationTest.groovy
Relax flaky test expectation

    • -3
    • +2
    ./resolve/override/ComponentOverrideMetadataResolveIntegrationTest.groovy
Relax flaky test expectation

    • -3
    • +2
    ./resolve/override/ComponentOverrideMetadataResolveIntegrationTest.groovy