CommandLineArgDeprecationIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Undeprecate --no-rebuild

A change in `buildSrc` causes the whole project to become out-of-date.

Thus, when making small incremental changes, the `--no-rebuild`

command-line option is often helpful to get faster feedback and is

therefore no longer deprecated.

Resolves #6968.

    • -71
    • +0
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 6 more files in changeset.
Remove --recompile-scripts option

The corresponding `StartParameter` property is now deprecated.

Resolves #6306.

    • -3
    • +0
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 23 more files in changeset.
Remove --recompile-scripts option

The corresponding `StartParameter` property is now deprecated.

Resolves #6306.

    • -3
    • +0
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 23 more files in changeset.
Expose deprecation warning messages and stacktraces via build operations (#5881)

Expose deprecation warnings as operation progress events

- introduce split of message, warning and advice

- make deprecation progress events immutable

- rework deprecation handling/messages to support more a richer model

- update build operation progress model

- tweak existing deprecation warnings to match new model

- Add performance test + make stacktrace calculation for build ops lazy

- Always include a trace with FeatureUsage now that its always required

    • -2
    • +2
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 65 more files 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>

    • -6
    • +2
    ./CommandLineArgDeprecationIntegrationTest.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
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 4 more files in changeset.
Rename WarningType to WarningMode

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

    • -8
    • +8
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 29 more files in changeset.
Add tests for warning options

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

    • -1
    • +1
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 4 more files in changeset.
Rebase master and polish up #3847

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

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

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

    • -12
    • +16
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 31 more files in changeset.
Remove usage of --no-search-upwards and deprecate

    • -1
    • +5
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 256 more files in changeset.
Render deprecation message for no-search-upward command line option

    • -1
    • +5
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 3 more files in changeset.
Refine deprecation mechanism (#3285)

Refine deprecation mechanism

Fix https://github.com/gradle/gradle/issues/3228

    • -4
    • +31
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 35 more files in changeset.
Deprecate --no-rebuild (#3077) (#3121)

https://github.com/gradle/gradle/issues/3077

This option was introduced in very early version of Gradle when up-to-date

checking was still rather expensive, which is no longer the case.

This PR now deprecates it.

    • -0
    • +39
    ./CommandLineArgDeprecationIntegrationTest.groovy
  1. … 8 more files in changeset.