Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Integ test should reuse kotlin compiler daemon

to prevent OOME

by not setting -Dkotlin.compiler.execution.strategy=in-process

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

Integ test should reuse kotlin compiler daemon

to prevent OOME

by not setting -Dkotlin.compiler.execution.strategy=in-process

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

Merge pull request #7663 from gradle/bamboo/release/kotlin-dsl-1.0.1

Upgrade Kotlin DSL to 1.0.1

Move services around for artifact transformations

So we only have one scope with the transformer invoker.

Move build scope id to cross build session services

This way we have only one build scope id per build session.

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Change the tooling API provider to route logging to the client stdout and stderr streams in a similar way to the command-line client.

When not producing rich output the tooling API writes errors to the stderr stream (same as when the command-line client is not run from a console), and when producing rich output the errors are written to the stdout stream (same as when the command-line client is run from a console).

Change the tooling API provider to route logging to the client stdout and stderr streams in a similar way to the command-line client.

When not producing rich output the tooling API writes errors to the stderr stream (same as when the command-line client is not run from a console), and when producing rich output the errors are written to the stdout stream (same as when the command-line client is run from a console).

Change the tooling API provider to route logging to the client stdout and stderr streams in a similar way to the command-line client.

When not producing rich output the tooling API writes errors to the stderr stream (same as when the command-line client is not run from a console), and when producing rich output the errors are written to the stdout stream (same as when the command-line client is run from a console).

Change the tooling API provider to route logging to the client stdout and stderr streams in a similar way to the command-line client.

When not producing rich output the tooling API writes errors to the stderr stream (same as when the command-line client is not run from a console), and when producing rich output the errors are written to the stdout stream (same as when the command-line client is run from a console).

Change the tooling API provider to route logging to the client stdout and stderr streams in a similar way to the command-line client.

When not producing rich output the tooling API writes errors to the stderr stream (same as when the command-line client is not run from a console), and when producing rich output the errors are written to the stdout stream (same as when the command-line client is run from a console).

Change the tooling API provider to route logging to the client stdout and stderr streams in a similar way to the command-line client.

When not producing rich output the tooling API writes errors to the stderr stream (same as when the command-line client is not run from a console), and when producing rich output the errors are written to the stdout stream (same as when the command-line client is run from a console).

Upgrade Kotlin DSL to 1.0.1

With proper IDE support for accessors involving default package types.

Publish 5.0-20181108000033+0000

Merge branch 'release' into 'master'

Change the tooling API provider to route logging to the stdout and stderr streams provided by the client in a similar way to the command-line client.

When not producing rich output (the default) the tooling API works the same way as `--console=plain` and when producing rich output the tooling API works the same way as `--console=rich`.

Reduce visibility of some test fixture types.

Reduce visibility of some test fixture types.

Reduce visibility of some test fixture types.

Reduce visibility of some test fixture types.

Reduce visibility of some test fixture types.

Reduce visibility of some test fixture types.

Do not attempt to invoke included build for task that has already executed

We were only tracking the tasks that had been _requested_ for execution.

With this change, we also track the tasks that are executed transitively.

This will make composite builds work in cases where the included build

provides a jar to the classpath of an including build, and the classes

directory to the implementation configuration of the same build.

Fixes #7650

Do not attempt to invoke included build for task that has already executed

We were only tracking the tasks that had been _requested_ for execution.

With this change, we also track the tasks that are executed transitively.

This will make composite builds work in cases where the included build

provides a jar to the classpath of an including build, and the classes

directory to the implementation configuration of the same build.

Fixes #7650

Display only BuildCacheKey.getHashCode()

Instead of using toString().