Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Cosmetics for incubating API tasks

Revert "Rebase `JavaFirstUsePerformanceTest` on latest nightly"

The rebase was done out of desperation to get the 5.0-milestone-1

released. It's most likely a bad rebase and we should investiguate if

it keep failing.

This reverts commit 7255bad6aab13455c50d1d21e56bce2c82bec40a.

Introduce an incubating APIs report

This commit adds an incubating APIs report to all Java projects. One

can get a report of the incubating APIs by running the `incubationReport`


An aggregate task, bound to `sanityCheck`, is also available:

- `allIncubationReportsZip` will generate a report aggregating all projects incubating APIs

- `allIncubationReports` will do the same but without a zip. This tasks is not bound to `sanityCheck`.

Merge pull request #6993 from gradle/lacasseio/kotlin/build-script-conversion

Convert build scripts to Kotlin

Add daily trigger to `Release - Snapshot` job.

So we can automatically publish its related metadata into `` to be consumed

by GE testing automation.

Fix link to task timeouts section

    • -1
    • +1
Fix link to task timeouts section

    • -1
    • +1
Reintroduce some limited synchronization for configuration resolution

This ensures that only one thread is resolving the graph of a given

configuration at a time.

When we step over to other projects while resolving configurations, we

will release the current project lock. This can allow other tasks to

start running. When they do, there can be issues when they try to

continue resolving the graph of the same configuration as the first

task. For example, a beforeResolve hook can cause the project lock

to be released (perhaps by resolving another configuration) and then

another task can put the configuration in an unexpected state before

the project lock can be reacquired..

Remove application plugin from misbehaving plugins

The application plugin now creates and references tasks lazily. As such,

the plugin can be removed from the list of misbehaving plugins in


Signed-off-by: Kevin Macksamie <>

Use lazy task API in the application plugin

Signed-off-by: Kevin Macksamie <>

Exclude application plugin from behaved plugins

With the ApplicationPluginIntegrationTest inheriting the tests from

WellBehavedPluginTest, it fails the "does not realize all possible

tasks" test. In order to make the test pass, the application plugin must

be included in the list of misbehaving plugins inside that test. This

confirms that the application plugin in its current state is not lazy.

Signed-off-by: Kevin Macksamie <>

Re-enable compatibility check

Revert "Revert "Clean accepted API changes""

This reverts commit 878b0ec5aa22ce6baa99f2536277cd0489a1d223.

Ignore broken tests

add test

Signed-off-by: Dan Sanduleac <>

Unblock CI by temporarily disabling binary check

We're trying to compare milestone vs unreleased RC

Test app plugin like other well behaved plugins

The application plugin neither creates its tasks lazily nor references

other tasks lazily (e.g., the `jar` task). Making the

ApplicationPluginIntegrationTest inherit from WellBehavedPluginTest

exposes this problem by showing that the plugin fails the "does not

realize all possible tasks" test.

Signed-off-by: Kevin Macksamie <>

Publish 5.0-milestone-1

Verify tests running in modular Java can access SLF4j

Use the daemon for native parallel tests

Take advantange of plugin accessors in samples

    • -1
    • +1
Merge pull request #1162 from gradle/bamboo/fix-default-package-task-accessors

Generate compilable accessors for tasks with types in the default package

Allow nicer constants for architecture tests

Parse Gradle public API

Generate compilable accessors for tasks with types in the default package

By explicitly importing task types from the default package in

the generated code.

Resolves #1158

Always realize configurations

as they can be used in fallback when attribute matching fails.

Fix "platform owners" not being serialized

Rebase `JavaFirstUsePerformanceTest` test on latest release nightly

Publish 5.0-20181002175355+0000

Rebase `JavaFirstUsePerformanceTest` on latest nightly