ApplicationIntegrationSpec.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix number of line to expect from start script

  1. … 1 more file in changeset.
Fix number of line to expect from start script

  1. … 1 more file in changeset.
Fix expected line count

Change more tests.

  1. … 20 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.

  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.

  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.

  1. … 98 more files in changeset.
Let integration tests in 'integ-test' not use deprecated configurations

  1. … 12 more files in changeset.
Let integration tests in 'integ-test' not use deprecated configurations

  1. … 12 more files in changeset.
Let integration tests in 'integ-test' not use deprecated configurations

  1. … 12 more files in changeset.
Let integration tests in 'integ-test' not use deprecated configurations

  1. … 12 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.

  1. … 162 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 283 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 284 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 285 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 285 more files in changeset.
Fix the expected number of lines in application start scripts

Create directories when registering outputs via the runtime API, too (#2929)

Previously we were creating output directories only for outputs registered via task property annotations.

  1. … 32 more files in changeset.
Cleanup stale output files during execution (#2572)

We now keep a registry of all the outputs generated by Gradle which will be reset on each version change. If Gradle encounters an existing output file, then it will remove it if is not part of the registered outputs and owned by Gradle/the build. We do also not remove directories containing outputs from different tasks.

The check to delete the stale outputs happens now just before the task executes and not up-front as it did before.

The `build` directory and all delete targets of the `clean` task are registered as owned by Gradle and are considered safe to delete.

Currently, the set of recorded task output files is only growing if we do not change the Gradle version. In the future we can improve on this by also detecting that some directories where removed (e.g. by running a clean task) and reflect this in the registry.

Fixes #1168

Fixes #973

+review REVIEW-6557

  1. … 32 more files in changeset.
Add integration test to check classpath order in generated start scripts (#2513)

    • -0
    • +47
    ./ApplicationIntegrationSpec.groovy
Run more tests with reproducible archives on

  1. … 11 more files in changeset.
Allow double quotes to be used inside start script arguments

The new argument handling in start scripts introduced with Gradle 3.2

(#621) uses double quotes (") to escape arguments. This breaks the usage

of double quotes inside of an argument. E.g.: `'-DFOO="bar < baz"'`

This is fixed by checking if either (") or (') is already used and

using the corresponding other character for escaping. The solution is

adopted from: www.etalabs.net/sh_tricks.html (Working with arrays)

Issue: #865

  1. … 5 more files in changeset.
Allow double quotes to be used inside start script arguments

The new argument handling in start scripts introduced with Gradle 3.2

(#621) uses double quotes (") to escape arguments. This breaks the usage

of double quotes inside of an argument. E.g.: `'-DFOO="bar < baz"'`

This is fixed by checking if either (") or (') is already used and

using the corresponding other character for escaping. The solution is

adopted from: www.etalabs.net/sh_tricks.html (Working with arrays)

Issue: #865

  1. … 5 more files in changeset.
Unix Start Script: do not escape VM options which are read from properties (and are therefore already escaped strings)

+review REVIEW-6235

  1. … 2 more files in changeset.
Corrected expected line count in start script tests

+review REVIEW-6235

  1. … 1 more file in changeset.
Limit ourselves to /bin/sh (#621)

+review REVIEW-6235

  1. … 3 more files in changeset.
Use old API methods for task inputs and outputs

Will revert deprecation in next commit.

+review REVIEW-6038

  1. … 38 more files in changeset.
GRADLE-3476 Removed 4NT-specific code in bat files

It's not necessary since it doesn't use SHIFT anymore, and actually

causes some parameters (those containing dashes, such as

"-Dorg.gradle.jvmargs=-Xmx2048m") to be processed incorrectly in

TCC/4NT.

  1. … 3 more files in changeset.