BasicProjectConfigurationProgressCrossVersionSpec.groovy

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let tooling-api cross-version tests not use deprecated configurations

    • -4
    • +4
    ./BasicProjectConfigurationProgressCrossVersionSpec.groovy
  1. … 17 more files in changeset.
Let tooling-api cross-version tests not use deprecated configurations

    • -4
    • +4
    ./BasicProjectConfigurationProgressCrossVersionSpec.groovy
  1. … 17 more files in changeset.
Let tooling-api tests not use deprecated configurations

    • -4
    • +4
    ./BasicProjectConfigurationProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Let tooling-api tests not use deprecated configurations

    • -4
    • +4
    ./BasicProjectConfigurationProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Let tooling-api tests not use deprecated configurations

    • -4
    • +4
    ./BasicProjectConfigurationProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Report TAPI progress events for project configuration

This commit introduces a new `OperationType.PROJECT_CONFIGURATION` and

adds specific `ProgressEvent` implementations. When the operation type

is not requested, no progress configuration events (neither as typed

events nor as generic build operations) will be reported. While that

will remove generic progress configuration events and their children

from clients that use old TAPI versions against Gradle >= 5.1, it is

consistent with the behavior for tasks and work items.

    • -0
    • +231
    ./BasicProjectConfigurationProgressCrossVersionSpec.groovy
  1. … 41 more files in changeset.