Donát Csikós

Let the Tooling API control system properties contributed from the client-side

5

Fixes #17745 Spec: https://docs.google.com/document/d/1eM8E_fajrCF_O-5R-_1VyCuPk4kpW5LJshqcrYZFoxo/edit# When a client executes a Gradle build invocation via the Tooling API, [all system properties](https://github.com/gradle/gradle/blob/master/subprojects/launcher/src/main/java/org/gradle/launcher/daemon/configuration/DaemonParameters.java#L154) from the client JVM are passed to the daemon. This is...

Fixes #1173 Fixes #? ### Context

This PR does not add any specific functionality but prepares further code changes to query arbitrary information from the target Gradle runtime such as: - association between tests classes and...

This fixes the deprecation warning reported at https://github.com/gradle/gradle/issues/17039#issuecomment-903113448.

Fixes #1023 ##### TODOs - [ ] Verify UI behavior on Windows.

This PR implements a new code mining extension point which adds a new shortcut to each supported editor that has a Gradle build file open.

`InitializeNewProjectOperation` passes the `--package` option to the `init` task, but the option was introduced in Gradle 5.0 only. ``` Expected no exception to be thrown, but got 'org.eclipse.core.runtime.CoreException' at spock.lang.Specification.noExceptionThrown(Specification.java:118)...

Transfer the source file encoding from Gradle to Eclipse

15

Original post: https://bugs.eclipse.org/bugs/show_bug.cgi?id=488947

The Build Scans ToS should be accessible from the UI. The user should have easy access to the ToS when enabling build scans.