Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'release' into bamboo/release/kotlin-dsl/9473

Merge remote-tracking branch 'origin/sg/60/wrapper-cleanup-fix' into release

* origin/sg/60/wrapper-cleanup-fix:

Avoid using the daemon on wrapper recovery test

Add more debug for Windows failure

Fix tooling-api unit test for distribution install

Re-try wrapper distribution installation when invalid

Mark a Gradle distribution unusable by the wrapper before deleting it

Merge remote-tracking branch 'origin/sg/60/log-format-date' into release

* origin/sg/60/log-format-date:

Fix timestamps in log

Use ISO 8601 log format for logged daemon messages

Add missing `@Incubating` annotation

Make `Project.plugins { }` extension a top-level function

Fail to compile nested `plugins` blocks in Kotlin scripts

Avoid using the daemon on wrapper recovery test

Add more debug for Windows failure

Merge pull request #10822 from gradle/bamboo/kotlin-dsl/implicit-receivers

Remove `Gradle`, `Settings` and `Project` interfaces from Kotlin DSL script type hierarchies

Fix timestamps in log

Fix tooling-api unit test for distribution install

Remove unnecessary import

Update error message for documentation check

Add compatibility note on precompiled script plugins

    • -0
    • +2
    /subprojects/docs/src/docs/release/notes.md
Merge branch 'release' into bamboo/kotlin-dsl/implicit-receivers

Merge pull request #10925 from gradle/eskatos/bincompat/do-not-ignore-deprecated

Stricter binary compatibility check of deprecated members

Prefer `Action<T>` over `T.() -> Unit` for the Kotlin script API

From the perspective of an user of the API both types are effectively

the same.

From a compile time and runtime perspective `Action<T>` seems a better

choice as values can be passed to the core Gradle API directly.

From an API consistency point of view `Action<T>` also looks like the

superior choice as it is more consistent with the rest of the Gradle

API.

And finally, from an user education perspective, `KotlinScript`

provides a clear opportunity for users to understand the equivalence

between `Action<T>` and `T.() -> Unit`.

Polish `ScriptApiTest`

Accept removal of deprecated members in FindBugsXmlReport

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

Accept removal of deprecated members in FindBugsReports

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

Accept removal of deprecated members in FindBugs

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

Fix realization of Maven metadata

The fix to handle SNAPSHOT dependencies correctly with Gradle

Module Metadata exposed a couple of failures in the "force

realize" cases, which correspond to the cases where metadata

has to be realized pre-emptively (using cached metadata rules

for example).

Accept removal of deprecated members in FindBugsExtension

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

Accept removal of deprecated members in FindBugsPlugin

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

Accept removal of deprecated members in JDependReports

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

Accept removal of deprecated members in JDepend

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

Accept removal of deprecated members in JDependExtension

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

Accept removal of deprecated members in JDependPlugin

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

Accept deprecated member made private in JacocoPlugin

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

Accept removal of deprecated members in JacocoReportBase

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