Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add support for failing on changing versions

This commit adds the `failOnChangingVersions()` method on

the resolution strategy, which will make the build fail as

soon as a changing version is detected.

This is useful to prevent, for example, snapshots from

appearing in a dependency graph.

  1. … 5 more files in changeset.
Add support for failing on changing versions

This commit adds the `failOnChangingVersions()` method on

the resolution strategy, which will make the build fail as

soon as a changing version is detected.

This is useful to prevent, for example, snapshots from

appearing in a dependency graph.

  1. … 5 more files in changeset.
Introduce `failOnDynamicVersion`

This commit introduces a new dependency graph validation mode,

which will make sure that if dynamic versions are found in the

graph, then either they are superceded by another version (they

don't participate in selection) or the build should fail.

This means that, for example, if a version selector uses a

version range `[1.0, 2.0[`, the build will fail because in a

subsequent build the resolution may change.

However, if there are two selectors participating, say

`[1.0, 2.0[` and `1.5`, then we choose `1.5` because this version

is within the range. Even if newer versions are released, we

would _not_ change the resolution result.

  1. … 8 more files in changeset.
Introduce `failOnDynamicVersion`

This commit introduces a new dependency graph validation mode,

which will make sure that if dynamic versions are found in the

graph, then either they are superceded by another version (they

don't participate in selection) or the build should fail.

This means that, for example, if a version selector uses a

version range `[1.0, 2.0[`, the build will fail because in a

subsequent build the resolution may change.

However, if there are two selectors participating, say

`[1.0, 2.0[` and `1.5`, then we choose `1.5` because this version

is within the range. Even if newer versions are released, we

would _not_ change the resolution result.

  1. … 8 more files in changeset.
Improve unsafe configuration resolution docs

  1. … 1 more file in changeset.
Improve unsafe configuration resolution docs

  1. … 1 more file in changeset.
Re-establish docs about constraints on dependency resolution

  1. … 1 more file in changeset.
Re-establish docs about constraints on dependency resolution

  1. … 1 more file in changeset.
Error when resolving configurations from user-managed threads

  1. … 1 more file in changeset.
Merge pull request #10286 from gradle/devisnk/make-detached-config-name-thread-safe

Use AtomicInteger for detached configuration name counter

Merge pull request #9353 from gradle/jjohannes/deprecate-java-configurations

Deprecate legacy configuration usages

Use AtomicInteger for detached configuration name counter

Signed-off-by: Volker Leck <volker@gradle.com>

Use AtomicInteger for detached configuration name counter

Signed-off-by: Volker Leck <volker@gradle.com>

Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

  1. … 1 more file in changeset.
Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

  1. … 2 more files in changeset.
Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

Do not yet deprecate configurations for both declaration and resolution

We may do this later when we offer an improved API.

https://github.com/gradle/gradle/issues/9834

Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some more indirection when locating the project to lock before running build logic that may access project state.

  1. … 15 more files in changeset.
Remove some indirection when locating the project to lock before running build logic that may access project state.

  1. … 8 more files in changeset.
Remove some indirection when locating the project to lock before running build logic that may access project state.

  1. … 8 more files in changeset.
Remove some indirection when locating the project to lock before running build logic that may access project state.

  1. … 8 more files in changeset.
Remove some indirection when locating the project to lock before running build logic that may access project state.

  1. … 8 more files in changeset.
Remove some indirection when locating the project to lock before running build logic that may access project state.

  1. … 8 more files in changeset.