DeprecationHandlingIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Start using explicit deprecation message checks

    • -1
    • +1
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix https://github.com/gradle/gradle-private/issues/2559

Very rarely the random groovy script name will contain `sun.` string.

    • -1
    • +1
    ./DeprecationHandlingIntegrationTest.groovy
Always add the deprecation failure to build result

Previously, the deprecation failure was reported only when there was no

other failure.

With these changes, it now always enhances the build result, possibly

making its failure a MultipleBuildFailures

    • -0
    • +23
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 1 more file in changeset.
Add integration test for warning mode fail

    • -1
    • +34
    ./DeprecationHandlingIntegrationTest.groovy
Fail on deprecation warning

* Adds one more option to warning-mode: fail

* If fail is activated, the build will fail at the end if any

deprecation warnings were reported

* Enhances the build result, possibly

making its failure a MultipleBuildFailures

Fixes #6491

    • -1
    • +32
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 4 more files in changeset.
Fail on deprecation warning

* Adds one more option to warning-mode: fail

* If fail is activated, the build will fail at the end if any

deprecation warnings were reported

* Enhances the build result, possibly

making its failure a MultipleBuildFailures

Fixes #6491

    • -1
    • +32
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 5 more files in changeset.
Fail on deprecation warning

* Adds one more option to warning-mode: fail

* If fail is activated, the build will fail at the end if any

deprecation warnings were reported

* Enhances the build result, possibly

making its failure a MultipleBuildFailures

Fixes #6491

    • -1
    • +32
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 5 more files in changeset.
Fail on deprecation warning

* Adds one more option to warning-mode: fail

* If fail is activated, the build will fail at the end if any

deprecation warnings were reported

* Enhances the build result, possibly

making its failure a MultipleBuildFailures

Fixes #6491

    • -1
    • +32
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 4 more files in changeset.
Fail on deprecation warning

* Adds one more option to warning-mode: fail

* If fail is activated, the build will fail at the end if any

deprecation warnings were reported

* Enhances the build result, possibly

making its failure a MultipleBuildFailures

Fixes #6491

    • -1
    • +32
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 4 more files in changeset.
Stack traces emitted by Gradle are stabilised to improve deduplication (#7859)

    • -15
    • +60
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 2 more files in changeset.
Stack traces emitted by Gradle are stabilised to improve deduplication

- filtering out all system stackframes from emitted stacktraces

    • -15
    • +60
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 2 more files in changeset.
Make deprecation summary actionable

See https://github.com/gradle/gradle/issues/4379.

    • -0
    • +2
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 1 more file in changeset.
Move warning summary to immediately before build summary

This makes it much more likely that the last 2 things the user will

see in order are: warning summary then build summary (then

build scan link, if configured)

Issue: #4042

Signed-off-by: Eric Wendelin <eric@gradle.com>

    • -2
    • +4
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 11 more files in changeset.
Change "there're" to "there are" in deprecation warnings

Signed-off-by: Eric Wendelin <eric@gradle.com>

    • -1
    • +1
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 4 more files in changeset.
Rename WarningType to WarningMode

Signed-off-by: Bo Zhang <bo@gradle.com>

    • -8
    • +8
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 29 more files in changeset.
Use warningType instead of warningTypes

Signed-off-by: Bo Zhang <bo@gradle.com>

    • -9
    • +8
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 24 more files in changeset.
Rebase master and polish up #3847

Signed-off-by: Bo Zhang <bo@gradle.com>

    • -8
    • +9
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 9 more files in changeset.
Add --warning to suppress deprecation warnings (#3726)

Signed-off-by: Bo Zhang <bo@gradle.com>

    • -75
    • +56
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 31 more files in changeset.
Explicitly declare org.gradle.util classes

    • -1
    • +1
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 3 more files in changeset.
Add hint about --stacktrace to deprecation warnings

#899

    • -0
    • +5
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 1 more file in changeset.
Enforce exact deprecation warning count

    • -8
    • +2
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 6 more files in changeset.
Fix test assertions now that we use doLast

+review REVIEW-6236

    • -4
    • +4
    ./DeprecationHandlingIntegrationTest.groovy
Use doLast instead of left shift operator

Made this change in preparation for deprecating the left shift operator.

+review REVIEW-6236

    • -4
    • +8
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 163 more files in changeset.
Fix init script integration test for deprecation logging

#689

+review REVIEW-6216

    • -5
    • +3
    ./DeprecationHandlingIntegrationTest.groovy
Fix forking integration test

The plugins in test fixtures cannot be used when forking a Gradle instance

I still need to look into how to fix the initscript test

#689

+review REVIEW-6216

    • -34
    • +65
    ./DeprecationHandlingIntegrationTest.groovy
Fix integration test

By reformatting the build scripts the lines changed by one

#689

+review REVIEW-6216

    • -18
    • +18
    ./DeprecationHandlingIntegrationTest.groovy
Polish logging stack of deprecation messages

#689

+review REVIEW-6216

    • -51
    • +49
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 7 more files in changeset.
Deprecation warning should print location in build file (#689)

    • -52
    • +114
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 17 more files in changeset.
Deprecating LoggingManager.setLevel()

+review REVIEW-5912

    • -0
    • +118
    ./DeprecationHandlingIntegrationTest.groovy
  1. … 34 more files in changeset.