TaskInputFilePropertiesIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 65 more files in changeset.
Fix ignored tests, take 2

    • -5
    • +5
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 2 more files in changeset.
Revert "Fix ignored tests"

    • -3
    • +6
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix ignored tests

    • -6
    • +3
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 2 more files in changeset.
Ignore failing tests temporarily

    • -0
    • +2
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 1 more file in changeset.
Re-use `TaskDependencyResolveContext` during task graph building (#3807)

All dependency resolution in Gradle should happen via TaskDependencyResolveContext during when building the task graph. Calling `DefaultTaskDependency.getDependencies(task)` should be avoided since it creates a new `TaskDependencyResolveContext` and needs to calculate the dependencies again.

`SkipTaskWithNoActionsExecuter` now re-uses the `TaskExecutionGraph` to determine the dependencies of a task instead of re-evaluating them.

After this commit, the task properties are resolved at three places:

- When building the task graph for walking the input files

- When checking if there a task can be executed in parallel with the currently running tasks based on on the declared outputs, destroyables and task local state

- For using the task properties during task execution

The last two places could still be unified into one, but that seems to be a little bit more complicated.

    • -1
    • +7
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 23 more files in changeset.
Remove deprecation of TaskInputs/Outputs query methods

Signed-off-by: Stefan Wolf <wolf@gradle.com>

    • -37
    • +0
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 5 more files in changeset.
Merge pull request #3793 from gradle/lptr/core/discover-task-dependency-via-buildable-input-files

Discover task dependencies via Buildable task inputs

    • -0
    • +34
    ./TaskInputFilePropertiesIntegrationTest.groovy
Deprecate TaskInputs.getProperties()

This method exposes internal state that is expensive to maintain.

There should be no need to query properties from user code, and

declaring new ones can be achieved via the property() and

properties() methods.

Signed-off-by: Lóránt Pintér <lorant@gradle.com>

    • -0
    • +1
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 3 more files in changeset.
Deprecate TaskOutputs.getHasOutput

This method expose internal state that is expensive to maintain.

Instead of using it, user code can rely on declared task properties.

Signed-off-by: Lóránt Pintér <lorant@gradle.com>

    • -0
    • +15
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 4 more files in changeset.
Discover task dependencies via Buildable task inputs

When registering task input files that implement Buildable and Iterable<File>,

now task dependencies are discovered via getBuildDependencies().

Signed-off-by: Lóránt Pintér <lorant@gradle.com>

    • -0
    • +34
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 1 more file in changeset.
Deprecate TaskInputs.getSourceFiles()

This method expose internal state that is expensive to maintain.

Instead of using them, user code can rely on declared task properties.

    • -0
    • +1
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 3 more files in changeset.
Deprecate access to TaskInputs.getHasInputs() and getHasSourceFiles()

These methods expose internal state that is expensive to calculate.

Instead of using them, user code can rely on declared task properties.

    • -0
    • +20
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 3 more files in changeset.
Show deprecation warning when incorrect input is used for runtime API (#3202)

Instead of failing the build when incorrect inputs are given to `TaskInputs.file()` and `dir()`, we show a deprecation warning.

    • -0
    • +26
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 3 more files in changeset.
Revert "Show deprecation warning when incorrect input is used for runtime API (#3199)"

This reverts commit 6399f1584e462388718cf8ff32bd96b5cec6e91d.

    • -26
    • +0
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 3 more files in changeset.
Show deprecation warning when incorrect input is used for runtime API (#3199)

Instead of failing the build when incorrect inputs are given to `TaskInputs.file()` and `dir()`, we show a deprecation warning.

    • -0
    • +26
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 3 more files in changeset.
Rename property spec classes to be clearer

+review REVIEW-6326

    • -4
    • +1
    ./TaskInputFilePropertiesIntegrationTest.groovy
  1. … 21 more files in changeset.
Test for optional null input file values

+review REVIEW-6326

    • -0
    • +48
    ./TaskInputFilePropertiesIntegrationTest.groovy