ExecutionTimeTaskConfigurationIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove Task#leftShift

Resolves #6266.

    • -13
    • +9
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 8 more files in changeset.
Remove Task.deleteAllActions

    • -37
    • +0
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 6 more files in changeset.
Fix test

    • -1
    • +37
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
Remove redundant deprecation warning expectations

    • -1
    • +1
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 24 more files in changeset.
Enforce exact deprecation warning count

    • -2
    • +1
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 6 more files in changeset.
Remove TaskOutputs.doNotCacheIf(Spec)

Must use the one with a reason.

    • -1
    • +0
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 4 more files in changeset.
Remove TaskInputs.source() and sourceDir()

    • -2
    • +0
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 5 more files in changeset.
Make `TaskOutputs.doNotCacheIf()` public

+review REVIEW-6382

    • -0
    • +2
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 3 more files in changeset.
Public runtime APIs for mapped plural task output properties

We’ve supported for some time `@OutputFiles` and `@OutputDirectories` properties with a `Map` type, where each output file or directory was mapped to a string identifier. However, this was only available via internal APIs and wasn’t documented. This commit exposes the runtime API via `TaskOutputs.files()` and the new `TaskOutputs.dirs()` methods.

+review REVIEW-6374

    • -4
    • +1
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 15 more files in changeset.
Handle `@OutputDirectories` as actual directories

+review REVIEW-6247

    • -0
    • +2
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 6 more files in changeset.
Deprecate left shift operator on Task

Change test cases accordingly.

+review REVIEW-6236

    • -0
    • +1
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 6 more files in changeset.
Rework plural task output registration APIs

We are reverting back to using the plural annotations `@OutputFiles` and `@OutputDirectories`, but only allow them to be used on `Map` properties (otherwise show a deprecation warning). The `Map` must associate a unique String identifier to each output file or directory, respectively.

This allows the removal of the recently introduced `configure()` methods on `TaskInputs` and `TaskOutputs`, but requires the introduction of the `TaskOutputs.namedFiles(Map)` method (and a version that takes a `Callable` to produce the map).

+review REVIEW-6055

    • -2
    • +2
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 35 more files in changeset.
Extend existing `TaskInputs`/`TaskOutputs` APIs instead of adding new ones

Previously new APIs were introduced with names like `includeFile()` and `includeDir()` that were slightly improved versions of the existing `file()` and `dir()` methods. The additional functionality was that they returned an object that could be used to configure the freshly registered property; whereas the old methods used to return a reference to `TaskInputs` or `TaskOutputs` to allow chaining the calls. The old methods were previously deprecated in favor of the new ones.

This commit removes the newly introduced `include*()` methods, and instead extends the existing ones. The tricky part is to keep compatible with the original method signatures while returning an object capable of configuring the property. To accomplish this, the property spec objects returned also implement `TaskInputs` and `TaskOutputs` to keep method chaining working. If chaining is used, a deprecation message is printed to warn the user to use `TaskInputs` or `TaskOutputs` directly instead.

+review REVIEW-6038

    • -5
    • +0
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 7 more files in changeset.
Revert "Temporarily reverting everything since 810f052813ea0835dc7e9d3eb87bca005815db64 for 3.0-milestone-1 release"

This reverts commit 506f8ce9d6dc1a81e8ff10575c512778ca2f382a.

    • -0
    • +5
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 199 more files in changeset.
Temporarily reverting everything since 810f052813ea0835dc7e9d3eb87bca005815db64 for 3.0-milestone-1 release

    • -5
    • +0
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 199 more files in changeset.
Bind task output files to properties

This change introduces a binding between task properties and output files. Output annotations automatically register property values to the corresponding property name.

The `TaskOutputs` API gained new methods with an `include` prefix that allow more flexible configuration of output properties, including specifying the property name to bind the files to. The old methods have been deprecated.

Properties that were not assigned a property name will be bound to a sequence of pseudo names like `$1`, `$2` etc.

+review REVIEW-6038

    • -0
    • +2
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 41 more files in changeset.
Bind task input files to properties

This change introduces a binding between task properties and input files. Input annotations automatically register property values to the corresponding property name.

The `TaskInputs` API gained new methods with an `include` prefix that allow more flexible configuration of input properties, including specifying the property name to bind the files to. The old methods have been deprecated.

Properties that were not assigned a property name will be bound to a sequence of pseudo names like `$1`, `$2` etc.

+review REVIEW-6038

    • -0
    • +3
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 33 more files in changeset.
Fix tests

+review REVIEW-6010

    • -0
    • +1
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 1 more file in changeset.
Forbid call to `TaskInputs/TaskOutputs.configure()` during execution

+review REVIEW-6010

    • -0
    • +2
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 2 more files in changeset.
Various Task, TaskInputs and TaskOutputs methods now fail when called after task execution has started. This behaviour was deprecated.

    • -130
    • +62
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 11 more files in changeset.
temporally fix failing integration tests for deprecations (TODO convert warnings to errors as claimed in our deprecation messages)

    • -62
    • +62
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
fix windows builds (2nd trial)

    • -1
    • +1
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
fix windows builds (first trial)

    • -62
    • +67
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
REVIEW-372: give hint about << just when running from a << closure.

    • -79
    • +121
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 2 more files in changeset.
REVIEW-404: use observable list to track action list changes during/after task execution.

    • -1
    • +18
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 2 more files in changeset.
REVIEW-374 fixed warning message.

    • -25
    • +25
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 1 more file in changeset.
REVIEW-366 don't throw exception if action is added to a task after/during excecution.

    • -20
    • +13
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 2 more files in changeset.
Review-368: add warning when deleteAllActions() is called after/during task execution.

    • -0
    • +2
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 1 more file in changeset.
GRADLE-2512: Add integration tests for warning messages.

    • -0
    • +105
    ./ExecutionTimeTaskConfigurationIntegrationTest.groovy
  1. … 1 more file in changeset.