Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Polish `execution.gradle.kts`

- Favour plugin accessor over string id for code navigation

Merge pull request #7669 from gradle/js/docs/remove-duplicate-heading

remove duplicate heading from release notes

remove duplicate heading from release notes

    • -2
    • +0
    /subprojects/docs/src/docs/release/notes.md
Upgrade Kotlin DSL to 1.0.2

Merge pull request #7667 from gradle/eskatos/perf/integ-tests-use-kotlin-compiler-daemon

Let integration tests not opt-in to in-process kotlin compiler

Correct Javadoc of SingleDepthFileAccessTracker

Spike new BuildProfileEvent

  1. … 15 more files in changeset.
Merge pull request #7610 from gradle/js/docs/start-upgrading-from-gradle-5.0-guide

Update release notes and upgrade guide to reflect 5.1 release

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.