CheckstylePluginVersionIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Ignore value of user provided config_loc in favor of configDirectory

This has been deprecated since May 2017

    • -3
    • +3
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 1 more file in changeset.
Remove use of deprecated property

    • -4
    • +4
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 1 more file in changeset.
Add configDirectory to Checkstyle

- Deprecate configDir

- Replace configDir with configDirectory

    • -0
    • +24
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 9 more files in changeset.
Add configDirectory to Checkstyle

- Deprecate configDir

- Replace configDir with configDirectory

    • -0
    • +24
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 9 more files in changeset.
Fix some tests.

    • -5
    • +5
    ./CheckstylePluginVersionIntegrationTest.groovy
Change more tests.

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 40 more files in changeset.
Fixes for changes to tests.

    • -3
    • +7
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 4 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -4
    • +8
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 50 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -9
    • +13
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -9
    • +13
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -4
    • +4
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 50 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -9
    • +13
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 98 more files in changeset.
Let antlr and code-quality tests not use deprecated configurations

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 10 more files in changeset.
Adjust integration tests to use 'implementation' instead of 'compile'

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 10 more files in changeset.
Let antlr and code-quality tests not use deprecated configurations

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 10 more files in changeset.
Adjust integration tests to use 'implementation' instead of 'compile'

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 10 more files in changeset.
Replace 'Matchers' with 'CoreMatchers'

So we do not require 'org.hamcrest:hamcrest-library' as additional

dependency anymore. Which was only available for most of the tests

because it leaked onto the test compile classpath.

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 162 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 283 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 284 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 285 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 285 more files in changeset.
Raise version to 5.0

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 24 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

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 65 more files in changeset.
Fix code quality usages of output test fixtures

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
Always report Checkstyle violations-summary from xml report (#3901)

Report Checkstyle violations from xml report, regardless of build pass/fail.

Prior to this, Checkstyle plugin would be silent unless the build failed or

ignoreFailures=true. If thresholds maxErrors and maxWarnings were not met,

reported rule violations in the XML or HTML reports were not mentioned in

build output.

With this change, if Checkstyle is configured to produce an XML report (default),

the report is parsed and violations summarised in the Checkstyle task build output.

This occurs regardless of whether the build failed or not.

Fixed #881

    • -0
    • +13
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 1 more file in changeset.
Add some more assertion methods to `ExecutionResult` and change several tests and utility methods to use these methods instead of reimplementing the logic.

    • -3
    • +3
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 11 more files in changeset.
Change int tests to use relevant fixture methods to express their expectations about the build log output.

    • -1
    • +5
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 28 more files in changeset.
Change int tests to use relevant fixture methods to express their expectations about the build log output.

    • -1
    • +1
    ./CheckstylePluginVersionIntegrationTest.groovy
  1. … 22 more files in changeset.