loader

Allow notifying about FS changes via the TAPI

This PR adds a new method to `ProjectConnection`, which sends a message

to all daemons and causes them to invalidate some part of the

retained file system state.

Apply `Explicit type can be replaced with <>` inspection the whole project

Add missing @Override to all modules

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

Remove support for connecting to Gradle <2.6

Suppress warnings for internal use of deprectated TAPI types

Named classloaders (#6834)

This should help give some more context while debugging classloading issues.

Introduce support for running phased actions

This commit introduces the ability of running multiple build actions in

different phases of the build. These actions are passed by the client

through the tooling api.

With this commit, a single action can be added to each one of the

supporting phases (after projects are loaded, after projects are

evaluated and after tasks are run).

This feature allows improvements like running actions that call a model

builder modifying the graph tasks, and then it is possible to first

fetch a model and then execute tasks, in this order. e.g. Android Studio

sync + source generation.

Signed-off-by: Lucas Smaira <lsmaira@google.com>

Parameter connection related code simplification

Renamings and code simplifications suggested in the pull request.

No functionality changed.

Deprecate support for old TAPI providers (#2913)

Deprecation TAPI provider older than 2.6

https://github.com/gradle/gradle-private/issues/898

This change deprecates running Gradle older than 2.6 via Tooling API

Introduce creation of parameterized tooling models

This commit introduces the possibility of passing parameters through the

Tooling API to the model builders in order to create models based on

information received by the client.

This feature allows plugins to register a model builder for a given

model and parameter and then build models based on the received

parameter. It is preferable to passing gradle properties for two

reasons: first convenience and second because parameters can be created

inside the BuildAction.

A new interface ToolingParameterizedModelBuilder was created and should

be extended by parameterized builders. New methods were added to the

BuildController in order to build models with parameters. In order to

keep cross version compatibility, new protocol interfaces were created.

Generate start and finish events for Gradle distribution download done by the TAPI.

Also moved responsibility for creating the downloader down closer to where the download happens, and inject only the listeners that are interested in the events.

tooling: report gradle wrapper download progress

Fail operation when target gradle doesn't support setting env vars

Removed some ClassLoader workarounds that were required for running the tooling API on IBM Java 5.

Remove GradleConnection API

The GradleConnection API was our first attempt at

implementing composite builds. We have improved on that

in Gradle 3.1, allowing the user to define composite builds

in settings.gradle and giving the user much more control

over how dependency substitution works.

A composite build is a normal Gradle build as far as the

Tooling API is concerned, so the separate concept of

the GradleConnection is no longer needed. We will add

methods for fetching all models from a composite build

to ProjectConnection in Gradle 3.2

Keep DefaultToolingImplementationLoader classloader open after change was clobbered by merge.

Leave Service classloader open between builds; we expect it.

Comment classloaders which are safe, close ones which leak.

Move classloader hashing to `ClassLoaderFactory`, step 1

This is to ensure that all classloaders created by the runtime are

hashed.

+review REVIEW-6010

Make `FilteringClassLoader` immutable

`SystemClassLoaderSpec` is moved to its own class so that it can be

included in `gradle-worker.jar`.

+review REVIEW-6020

Removed support for invoking Gradle versions older than 1.2 through tooling API. This is now an error.

Cache `ServiceLocator` results

This commit introduces a cached service locator which is used when the locator is going to be called several times on the same classloader. This is the case for plugins, typically. This reduces the cost of project initialization.

+review REVIEW-5956

Issue a deprecation warning when using the tooling API to run a build using Gradle 1.1 or older. This will be changed to an error in Gradle 3.0.