PluginApplicationBuildProgressCrossVersionSpec.groovy

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

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

    • -2
    • +2
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +54
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +54
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +53
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +53
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +53
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +54
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 more files in changeset.
Use 'java-library' and 'api' as defaults for buildSrc

    • -2
    • +53
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 3 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.

    • -1
    • +1
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 41 more files in changeset.
Remove support for TAPI clients <3.0

    • -2
    • +0
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 63 more files in changeset.
Fix test

    • -2
    • +2
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
Fix attribution bug for listeners in allprojects

This also changes behaviour to only emit a single listener execution op

per allprojects listener registered, and removes an extra rootProject

listener execution op in the op chain that was misleading.

    • -3
    • +2
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 2 more files in changeset.
Fix cross-version test version spec

    • -2
    • +2
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
Expose insights to build script compilation (#6097)

    • -3
    • +0
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 9 more files in changeset.
Use external repository mirrors in build (#6094)

We've been bitten by external repository fluctuation for a long time.

This PR makes most of tests use repository mirrors set up by ourselves

via init script and system property.

There're still some tests not switching to mirrors, which would be fixed

in follow-up commits.

    • -1
    • +3
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 99 more files in changeset.
Add listener name to operation

    • -9
    • +3
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 9 more files in changeset.
Fix cross version test

    • -2
    • +83
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
Recover ignored tests

See https://github.com/gradle/gradle-private/issues/1341

and https://github.com/gradle/gradle/issues/5777

Recover these tests after jfrog adjusted their cipher configuration

    • -5
    • +0
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 6 more files in changeset.
    • -0
    • +5
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
    • -0
    • +5
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
Fix TAPI integration tests

    • -1
    • +1
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 2 more files in changeset.
Rename tapiTest to crossVersionTest and apply review comments

    • -0
    • +470
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 349 more files in changeset.
Allow script plugins to be applied via the plugins DSL

Remote URLs are also supported:

```

plugins {

script "path/to/other.gradle"

script "https://example.com/another.gradle"

}

```

Local file paths are expressed as relative from the requesting script.

Constrain plugins {} block api to distinguish binary and script

plugin requests by both strongly modeled types and ad-hoc groovy parsing

of the plugins block. This pave the way for proper support of the

plugins {} block with the Gradle Kotlin DSL.

Implement ScriptPlugin PluginResolver by generating a synthetic

"imperative" Plugin class that loads and applies the script plugin when

applied.

This synthetic generated loader class and the script plugins are loaded

into the buildSrc classloader scope.

Only Project targets are supported.

`apply false` is not supported.

    • -1
    • +1
    ./PluginApplicationBuildProgressCrossVersionSpec.groovy
  1. … 64 more files in changeset.