Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge remote-tracking branch 'origin/release'

* origin/release:

Make Zinc version constant public

Fix TAPI tests

Pin santaTracker to older version

Typo: signatures -> checksums

Fix TAPI test for Maven upload events

Fix unit test

Add tests to prove resiliency of SHA signature uploads

Fix signing test cases

Add support for sha256/sha512 to ivy publishing

Add sha-256 and sha-512 checksums to `maven-publish`

Update docs to say Scala 2.13 can be compiled

Add test coverage for Scala 2.13

Upgrade to Kotlin 1.3.50

Track input files in build scans

Do not clone twice from remote

Do not check out default branch

Simplify enabling the publishing of a build scan

Update results for AGP 3.6.0-beta01

Add results for AGP 3.5.0 with Kotlin 1.3.50

Add special cases for 1 and 2 children

Add special cases for 1 and 2 children

Add special cases for 1 and 2 children

Add special cases for 1 and 2 children

Fix for changes.

Kill all daemons after test

Kill all daemons after test

Mention deprecation in upgrade guide.

Mention deprecation in upgrade guide.

Mention deprecation in upgrade guide.

Mention deprecation in upgrade guide.

Remove trailing space in error message

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

Remove trailing space in error message

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

Remove trailing space in error message

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

Remove trailing space in error message

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

Remove trailing space in error message

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

Remove trailing space in error message

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

Add magic system property so testkit dir can be cleaned up

Introduce concept of LockMode

Will allow users to define the lock mode under which a build needs to

operate:

* DEFAULT is the way locking worked up to Gradle 6.0

* STRICT is a new mode where the resolution will fail if a dependency is

marked as locked but does not have a lock state associated.

* LENIENT is a new mode where the lock state will be used to prevent

auto upgrades of version but the validation step is skipped, allowing a

developer to work on the project without having to update the lock state

after every change impacting resolution

Issue #9907

Introduce concept of LockMode

Will allow users to define the lock mode under which a build needs to

operate:

* DEFAULT is the way locking worked up to Gradle 6.0

* STRICT is a new mode where the resolution will fail if a dependency is

marked as locked but does not have a lock state associated.

* LENIENT is a new mode where the lock state will be used to prevent

auto upgrades of version but the validation step is skipped, allowing a

developer to work on the project without having to update the lock state

after every change impacting resolution

Introduce concept of LockMode

Will allow users to define the lock mode under which a build needs to

operate:

* DEFAULT is the way locking worked up to Gradle 6.0

* STRICT is a new mode where the resolution will fail if a dependency is

marked as locked but does not have a lock state associated.

* LENIENT is a new mode where the lock state will be used to prevent

auto upgrades of version but the validation step is skipped, allowing a

developer to work on the project without having to update the lock state

after every change impacting resolution

Introduce concept of LockMode

Will allow users to define the lock mode under which a build needs to

operate:

* DEFAULT is the way locking worked up to Gradle 6.0

* STRICT is a new mode where the resolution will fail if a dependency is

marked as locked but does not have a lock state associated.

* LENIENT is a new mode where the lock state will be used to prevent

auto upgrades of version but the validation step is skipped, allowing a

developer to work on the project without having to update the lock state

after every change impacting resolution

Issue #9907

Introduce concept of LockMode

Will allow users to define the lock mode under which a build needs to

operate:

* DEFAULT is the way locking worked up to Gradle 6.0

* STRICT is a new mode where the resolution will fail if a dependency is

marked as locked but does not have a lock state associated.

* LENIENT is a new mode where the lock state will be used to prevent

auto upgrades of version but the validation step is skipped, allowing a

developer to work on the project without having to update the lock state

after every change impacting resolution

Use binary search to find children

Use binary search to find children

Use binary search to find children

Don't check root path handling on Windows

Don't check root path handling on Windows

Don't check root path handling on Windows