Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Merge pull request #12857 from gradle/eskatos/kotlin-dsl/prepare-task-root-project

Let Kotlin DSL model preparation task be registered on the root project only

Publish 6.4-20200421152022+0000

Apply the 'classycle' plugin consistently to all projects (#12849)

Existing cycles are now explicitly excluded in the corresponding

build scripts and are thus more visible. They may or may not be

improved on when working on the corresponding project.

  1. … 76 more files in changeset.
Also register KotlinDslScriptsModelBuilder on root project only

Signed-off-by: Paul Merlin <>

Merge pull request #12846 from gradle/eskatos/testkit/restore-compatiblity-tests

Restore TestKit multi-version compatibility tests

Update keyring

Merge branch 'release'

Use Gradle OperatingSystem utility

Merge remote-tracking branch 'origin/vv/fix-cygwin-xterm-console'

* origin/vv/fix-cygwin-xterm-console:

Fix a typo, remove unneeded public modifiers

Use Windows console settings for Cygwin

Don't discard the Jar manifest when transforming plugin classes.

Add some more test coverage for undeclared system property read from statically compiled plugins in `buildSrc`.

Publish 6.4-20200420230449+0000

Revert changes to internal handling of JavaExec.classpath (#12852)

This suffers from:

The revert fixes:

Merge pull request #12848 from gradle/vv/use-plugins-dsl-in-javadocs

Use plugins DSL in Javadoc code snippets

Merge pull request #12850 from gradle/vv/document-external-plugins-in-precompiled-plugins

Document how to apply external plugins in precompiled plugins

Add @LeaksFileHandles to GradleRunnerDaemonIntegrationTest

Signed-off-by: Paul Merlin <>

Adjust cross version TAPI tests expectations for implicit tasks

Signed-off-by: Paul Merlin <>

Kotlin DSL model preparation task on root project only

Signed-off-by: Paul Merlin <>

Apply the Java derivation strategy to the Java Platform plugin

This commit makes sure that the Java Platform plugin also applies the

Java derivation strategy, as it, as it names indicates, also belongs

to the Java ecosystem. Not doing so triggers some weird ordering issues

if another project, which is a Java library, tries to resolve the same

dependencies as the Java platform, but after the platform has resolved


Because of component metadata caching, the first project to resolve

a dependency will be the "source of truth" for dependency metadata for

the module for the whole build. It means that if it was a Java library,

then the derivation strategy was applied and the project could resolve

everything properly. However, if the first project to trigger resolution

of a module was a Java Platform, then we would cache component metadata

_without_ derivation. This means, in particular, that platforms wouldn't

be derived for external Maven modules.

This explains why in #12728, order of execution of tasks matters: if

the subproject was resolved _first_ (gradle sub:compileJava resolve)

then everything was fine, but if the platform was resolved first, then

the rest of the build would fail.

The fix is to apply the derivation strategy to the Java platform plugin

too. However, in an ideal world, we should refactor the Java plugins so

that they consist of several layers:

- a "schema" layer, configuring the ecosystem schema, the derivation strategy, ...

- a "base" layer, consisting of what the Java Base plugin does today

- a "platform", directly on top of "schema"

- an application, and a "library", on top of "base"

Fixes #12728

Re-enable VFS retention soak tests

These have been fixed by #12746.

Merge pull request #12826 from gradle/eskatos/ie/registered-outputs

Let instant execution capture registered task outputs for stale outputs cleanup

Fix GradleRunnerDaemonIntegrationTest

--warning-mode is available starting with Gradle 4.5

Signed-off-by: Paul Merlin <>

Fix GradleRunner(Conventional)PluginClasspathInjectionIntegrationTest

Plugin not found resolution error message changed starting with

Gradle 4.4

Signed-off-by: Paul Merlin <>

Fix GradleRunnerResultIntegrationTest

script under test was changed to use an api not available in minimum

supported gradle version

Signed-off-by: Paul Merlin <>

Fix GradleRunnerMechanicalFailureIntegrationTest

spurious blank line

Signed-off-by: Paul Merlin <>

Document how to apply an external plugin in precompiled script plugin

Fix TestKit compatibility tests target version selection

to use the minimum target Gradle version supported by the tests

according to the used features captured as annotations

This change makes more tests run with minimum supported versions.

Signed-off-by: Paul Merlin <>

Relative 'gradle_installPath' is resolved relative to root project path

Fix GradleRunnerBuildFailureIntegrationTest

Grouped task output is available in TestKit output starting with Gradle 5.0

--warning-mode is available starting with Gradle 4.5

Signed-off-by: Paul Merlin <>

Fix GradleRunnerMechanicalFailureIntegrationTest

to account for console output changes in Gradle 4.0

Signed-off-by: Paul Merlin <>