TaskPropertyNamingIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove PropertySpecFactory

    • -2
    • +2
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 33 more files in changeset.
Adapt visitLocalStateProperty

    • -2
    • +2
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 12 more files in changeset.
Adapt visitDestroyableProperty

    • -2
    • +2
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 8 more files in changeset.
Adapt visitOutputFileProperty

    • -5
    • +5
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 34 more files in changeset.
Adapt visitInputProperty

    • -2
    • +2
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 15 more files in changeset.
The visitor should handle all the creation

Especially the annotation handler should not need the file resolver.

    • -3
    • +3
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 44 more files in changeset.
Don't use propertySpecFactory for input files

    • -7
    • +7
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 51 more files in changeset.
Ignore `@Nested` properties when attaching output file `Property` instances to their producing task.

This is a work around to avoid the performance cost of `@Nested` property getters that throw exceptions when called immediately after the task is created. These issues will be addressed later and better support for output file `Property` properties attached to nested beans added.

    • -1
    • +1
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 12 more files in changeset.
Track implementation without trailing `.class`

    • -7
    • +7
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 8 more files in changeset.
Do not restart unnamed property counter

When unnamed properties are assigned a name like etc., we now keep track

of the last number assigned, and if more unnamed properties are registered,

we don't restart counting from , resulting in property name collisions.

    • -0
    • +79
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 9 more files in changeset.
Start nested iterable naming from zero

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

    • -3
    • +3
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 3 more files in changeset.
Use `.class` instead of `.$$implementation` for nested property implementation (#3965)

Instead of introducing a new generated property for nested beans we

should re-use the `.class` property which is already present.

    • -4
    • +2
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 8 more files in changeset.
Allow rich Java compiler arguments (#3858)

This allows adding richer compiler arguments to JavaCompile.

    • -16
    • +57
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 30 more files in changeset.
Don't use now deprecated getProperties() method

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

    • -47
    • +67
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 6 more files in changeset.
Support rich task inputs (#3720)

@Nested inputs are now discovered based on the runtime type instead of the static type.

    • -1
    • +189
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 150 more files in changeset.
Detect changes between null output file and non-existent output file (#3079)

We need to distinguish between an optional output file property which

is `null` and a property which points to some non-existent files.

The easiest way to do so is to remove optional output properties which

are `null` completely.

We break some tests now that we distinguish the order in which the

output files are declared.

    • -3
    • +6
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 9 more files in changeset.
Fix test

There was a typo.

+review REVIEW-6205

    • -1
    • +1
    ./TaskPropertyNamingIntegrationTest.groovy
No sub-properties for plural output properties

In 3.0 we introduced auto-generated pseudo-sub-properties for each file in a `@OutputDirectories` or `@OutputFiles` property (or files registered via `TaskOutputs.files()`). These pseudo-sub-properties used to take names like `someProperty$1` etc. This commit reverts that change. Instead we disable caching for tasks that employ output properties with multiple files/directories.

+review REVIEW-6205

    • -6
    • +11
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 10 more files in changeset.
Fix test

Order of files listed in an input directory is not consistent, we need to sort them to make sure we get the same result every time.

+review REVIEW-6204

    • -2
    • +2
    ./TaskPropertyNamingIntegrationTest.groovy
Test nested properties as well

+review REVIEW-6204

    • -0
    • +16
    ./TaskPropertyNamingIntegrationTest.groovy
Fix plural output property naming bug

+review REVIEW-6204

    • -0
    • +82
    ./TaskPropertyNamingIntegrationTest.groovy
  1. … 1 more file in changeset.