Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use a relative path to a build script that is used as a the location for a configuration cache problem.

  1. … 33 more files in changeset.
Update feature preview name

Change from VERSION_SORTING_V2 to VERSION_ORDERING_V2

  1. … 6 more files in changeset.
Update feature preview name

Change from VERSION_SORTING_V2 to VERSION_ORDERING_V2

  1. … 5 more files in changeset.
DSL tweaks

  1. … 3 more files in changeset.
Rename `VariantArtifactSelector` -> `DependencyArtifactSelector`

  1. … 3 more files in changeset.
Fix dependency relocation todo

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

Fix previous commit.

  1. … 7 more files in changeset.
Fix previous commit.

  1. … 7 more files in changeset.
Fix previous commit.

  1. … 7 more files in changeset.
Add an Override annotation for provided credentials in repository class

Expose credentials providers for authenticated repositories

  1. … 6 more files in changeset.
Move credentials provider factory interface to core-api module

  1. … 12 more files in changeset.
Merge branch 'master' into vv/credentials-providers-v2

Integrate review suggestions

Issue #13050

  1. … 5 more files in changeset.
Integrate review suggestions

Issue #13050

  1. … 5 more files in changeset.
Integrate review suggestions

Issue #13050

  1. … 5 more files in changeset.
Integrate review suggestions

Issue #13050

  1. … 5 more files in changeset.
Integrate review suggestions

Issue #13050

  1. … 5 more files in changeset.
Update behaviour for exclude upper bound in range

The upper bound of a version range, when it is an exclusion, now acts as

a smart prefix. Versions that were excluded before remain excluded. In

addition, versions that start with the upper bound are also excluded.

This resolves the unexpected case where 2.0-dev1 is included when the

upper bound is 2.0[.

Fixes #13050

  1. … 4 more files in changeset.
Update behaviour for exclude upper bound in range

The upper bound of a version range, when it is an exclusion, now acts as

a smart prefix. Versions that were excluded before remain excluded. In

addition, versions that start with the upper bound are also excluded.

This resolves the unexpected case where 2.0-dev1 is included when the

upper bound is 2.0[.

Fixes #13050

  1. … 4 more files in changeset.
Provide using a single method accepting the type instead of multiple per-type methods

  1. … 4 more files in changeset.
Simplify credentials provider with inferred identity from repository

  1. … 4 more files in changeset.
Simplify credentials provider with inferred identity from repository

  1. … 5 more files in changeset.
Make classifier substitution available to `eachDependency`

Classifier (and more generally artifact substitution) is now possible

using the legacy `eachDependency` API. While we shouldn't encourage

use of this if `dependencySubstitutions` can be used, it's important

to be on par.

  1. … 6 more files in changeset.
Make classifier substitution available to `eachDependency`

Classifier (and more generally artifact substitution) is now possible

using the legacy `eachDependency` API. While we shouldn't encourage

use of this if `dependencySubstitutions` can be used, it's important

to be on par.

  1. … 6 more files in changeset.
Make classifier substitution available to `eachDependency`

Classifier (and more generally artifact substitution) is now possible

using the legacy `eachDependency` API. While we shouldn't encourage

use of this if `dependencySubstitutions` can be used, it's important

to be on par.

  1. … 7 more files in changeset.
Make classifier substitution available to `eachDependency`

Classifier (and more generally artifact substitution) is now possible

using the legacy `eachDependency` API. While we shouldn't encourage

use of this if `dependencySubstitutions` can be used, it's important

to be on par.

  1. … 6 more files in changeset.
Avoid resolving a repository url eagerly

Given we only need the repository name for error messages, there is

no need to resolve it directly (which also resolves the url of the

repository which may be a provider).

Fixes #13152

  1. … 2 more files in changeset.
Avoid resolving a repository url eagerly

Given we only need the repository name for error messages, there is

no need to resolve it directly (which also resolves the url of the

repository which may be a provider).

Fixes #13152

  1. … 2 more files in changeset.
Simplify repository credentials identity resolution