ProjectConfigurationChildrenProgressCrossVersionSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'master' into feature/JLL/depricate_http_download_dependencies

* master: (77 commits)

Realized component variants need to provide all attributes

Fix TeamCity Hygiene failures

New performance process (#10361)

Publish 5.6.1-20190825230025+0000

Publish 5.6.1-20190824230038+0000

Update .com userguide links

Update .com footer links

Update .com header links

Publish 5.6.1-20190823234015+0000

Rebase to latest 6.0 nightly

Revert "Recognize contributor"

Remove use of Java 11 API from instant execution

Recognize contributor

enhanced test source folder detection for eclipse task. (#10320)

Publish 5.6.1-20190823130927+0000

Rebase performance tests with 5.7-20190812122716+0000 baseline

Upgrade wrapper to 6.0 nightly

Rebase performance tests with 5.7-20190722220035+0000 baseline

Rebaseline to lock performance improvements

Temporarily use 5.6 as the baseline for Santa Tracker `assembleDebug` case.

...

    • -3
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 17 more files in changeset.
Align implementations of artifact identifier display names

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name).

This means that the artifact name used during reporting now

contains the version at the usual position in the file name.

This way it shows the actual file name for artifacts originating

from pom-only maven repositories (except snapshots, which show the

SNAPSHOT placeholder) and ivy repositories with default pattern.

The motivation for this alignment is to get the same representation for

the same file, independent of whether it was sourced from traditional

or Gradle module metadata.

    • -3
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 32 more files in changeset.
Align implementations of artifact identifier display names

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name).

This means that the artifact name used during reporting now

contains the version at the usual position in the file name.

This way it shows the actual file name for artifacts originating

from pom-only maven repositories (except snapshots, which show the

SNAPSHOT placeholder) and ivy repositories with default pattern.

The motivation for this alignment is to get the same representation for

the same file, independent of whether it was sourced from traditional

or Gradle module metadata.

    • -3
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 32 more files in changeset.
Revert "Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'""

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

    • -8
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 90 more files in changeset.
Revert "Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'""

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

    • -8
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 90 more files in changeset.
Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'"

This reverts commit 2f79026f5e127a8175e25844522237615b19ed52 because of a performance regression,

reversing changes made to 7f1e66079ce629ecde3e09e549e9796ab85761dc.

    • -8
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 90 more files in changeset.
Fixes failing ProjectConfigurationChildrenProgressCrossVersionSpec test

    • -8
    • +8
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
Let tooling-api cross-version tests not use deprecated configurations

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

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

    • -16
    • +16
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 6 more files in changeset.
Let tooling-api tests not use deprecated configurations

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

    • -16
    • +16
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 6 more files in changeset.
Let tooling-api tests not use deprecated configurations

    • -16
    • +16
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 6 more files in changeset.
Let tooling-api tests not use deprecated configurations

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

    • -16
    • +16
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 19 more files in changeset.
Let 'does not generate events for non-existing build scripts' test be more precise and resilient

by actually testing there's no script event

instead of asserting on a magic number of events that encompass

the combinations of tapi versions and target gradle versions

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

    • -1
    • +3
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
Update `ProjectConfigurationChildrenProgressCrossVersionSpec`

To take the newly introduced `prepareKotlinBuildScriptModel` task into

account.

Signed-off-by: Rodrigo B. de Oliveira <rodrigo@gradle.com>

    • -1
    • +1
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
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
    • +385
    ./ProjectConfigurationChildrenProgressCrossVersionSpec.groovy
  1. … 41 more files in changeset.