DefaultProjectConnectionTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename

  1. … 6 more files in changeset.
Fix issue reported by sanityCheck

  1. … 2 more files in changeset.
Fix and re-enable test

Make DefaultGradleConnector.disconnect() non-static

  1. … 5 more files in changeset.
Add daemon shutdown functionality to DefaultGradleConnector

  1. … 25 more files in changeset.
Add daemon shutdown functionality to DefaultGradleConnector

  1. … 26 more files in changeset.
Add daemon shutdown functionality to DefaultGradleConnector

  1. … 25 more files in changeset.
Add daemon shutdown functionality to DefaultGradleConnector

  1. … 26 more files in changeset.
Remove public PhasedBuildActionExecutor type

The type behaves just like a regular build action

except that it can hook into different phases of

the build.

  1. … 18 more files in changeset.
Rename phasedAction() to action()

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

  1. … 3 more files in changeset.
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>

  1. … 54 more files in changeset.
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

  1. … 136 more files in changeset.
Unit test fixes

  1. … 3 more files in changeset.
Renamed a bunch of consumer classes.

  1. … 29 more files in changeset.
Changed tooling API so that model types don't need to extend `Model`.

  1. … 7 more files in changeset.
Moved the adapting from protocol object to model object down closer to the provider, so that the adapting can be done based on the provider version.

  1. … 6 more files in changeset.
Moved the mapping from model to protocol type down to ModelProvider. This happens after we've spun up the provider (potentially downloading it) so that we can ask it questions about whether the model is supported.

    • -14
    • +1
    ./DefaultProjectConnectionTest.groovy
  1. … 6 more files in changeset.
Shuffled around some tooling API classes. In particular, moved ProtocolToModelAdapter out of the consumer hierarchy as it is used by both the consumer and provider.

  1. … 26 more files in changeset.
Moved some comlexity out of the ProtocolToModelAdapter so that it knows less about the domain model. It still knows about VersionDetails but I think I can fix that...

  1. … 10 more files in changeset.
Remove org.gradle.tooling.model.Project.

  1. … 17 more files in changeset.
Busted some classes to separate packages inside the tooling api consumer.

  1. … 21 more files in changeset.
Improved exception when tooling api client asks for unknown model.

  1. … 3 more files in changeset.
Changed ConcurrentSpecification to use a (hopefully) simpler dsl, and to give much better error messages.

  1. … 5 more files in changeset.
Some tooling API changes: - Lazily download the Gradle distribution as part of the first long running operation, rather than on connection creation. - Simplified cross-version tooling interfaces, by making them synchronous. Deal with the asynch stuff in the consumer implementation. - Tightened up thread safety in the consumer implementation.

    • -35
    • +1
    ./DefaultProjectConnectionTest.groovy
  1. … 20 more files in changeset.
Some changes to the cross-version tooling interfaces, to merge ConnectionFactoryVersion4 and ConnectionVersion4.

  1. … 31 more files in changeset.
GRADLE-1417 - Allow stdout and stderr to be captured when building a model via the tooling api.

    • -103
    • +11
    ./DefaultProjectConnectionTest.groovy
  1. … 12 more files in changeset.
GRADLE-1340 - Added the ability to execute a build via the tooling API - Better defined exception handling across the tooling API - Fixed problem where 'eclipse plugin not found' exception was thrown when build execution or model building failed.

    • -3
    • +23
    ./DefaultProjectConnectionTest.groovy
  1. … 31 more files in changeset.
GRADLE-1421 - Added path and description properties to tooling api project and task domain objects. - Some improvements to error message when invalid Gradle distribution is specified - Renamed ConnectionVersion2 -> ConnectionVersion3.

  1. … 31 more files in changeset.
GRADLE-1421, GRADLE-1455 - Allow client of tooling api to ask for the basic project hierarchy without all the details, such as external dependencies. The implementation still builds the whole model, for now. - Allow client of tooling api to ask for the tasks of a project. - Renamed protocol interfaces as they changed.

  1. … 29 more files in changeset.
- Incremented tooling API protocol number prior to milestone release. - Improved reporting when attempting to use an unsupported Gradle distribution via the tooling API. - Some tweaks to GradleVersion.

    • -11
    • +11
    ./DefaultProjectConnectionTest.groovy
  1. … 46 more files in changeset.