TaskPropertiesIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixes.

    • -2
    • +2
    ./TaskPropertiesIntegrationTest.groovy
Deprecate `AbstractTask` for removal in Gradle 7.0.

    • -2
    • +2
    ./TaskPropertiesIntegrationTest.groovy
  1. … 4 more files in changeset.
Deprecate `AbstractTask` for removal in Gradle 7.0.

    • -2
    • +2
    ./TaskPropertiesIntegrationTest.groovy
  1. … 4 more files in changeset.
Deprecate `AbstractTask` for removal in Gradle 7.0.

    • -2
    • +2
    ./TaskPropertiesIntegrationTest.groovy
  1. … 4 more files in changeset.
Fixes for previous commit.

    • -1
    • +1
    ./TaskPropertiesIntegrationTest.groovy
Fixes for previous commit.

    • -1
    • +1
    ./TaskPropertiesIntegrationTest.groovy
Fixes for previous commit.

    • -1
    • +1
    ./TaskPropertiesIntegrationTest.groovy
Fixes for previous commit.

    • -1
    • +1
    ./TaskPropertiesIntegrationTest.groovy
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 7 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 7 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Attach a display name to the value of a read-only `@Nested` property when value is not managed.

This changes means `@Nested` properties are treated the same way as properties whose type is a 'lazy' type.

    • -0
    • +35
    ./TaskPropertiesIntegrationTest.groovy
  1. … 8 more files in changeset.
Fix class generation to handle the bridge methods that are sometimes generated by the Java compiler in a subclass to override a concrete method in an abstract super class.

    • -0
    • +50
    ./TaskPropertiesIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix class generation to handle the bridge methods that are sometimes generated by the Java compiler in a subclass to override a concrete method in an abstract super class.

    • -0
    • +50
    ./TaskPropertiesIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix class generation to handle the bridge methods that are sometimes generated by the Java compiler in a subclass to override a concrete method in an abstract super class.

    • -0
    • +50
    ./TaskPropertiesIntegrationTest.groovy
  1. … 2 more files in changeset.
Fixes for previous commit.

    • -26
    • +26
    ./TaskPropertiesIntegrationTest.groovy
  1. … 11 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

    • -26
    • +26
    ./TaskPropertiesIntegrationTest.groovy
  1. … 35 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

    • -26
    • +26
    ./TaskPropertiesIntegrationTest.groovy
  1. … 35 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

    • -26
    • +26
    ./TaskPropertiesIntegrationTest.groovy
  1. … 35 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

    • -26
    • +26
    ./TaskPropertiesIntegrationTest.groovy
  1. … 35 more files in changeset.
Support managed properties of type `DomainObjectSet<T>`.

    • -0
    • +31
    ./TaskPropertiesIntegrationTest.groovy
  1. … 6 more files in changeset.
Support managed properties of type `DomainObjectSet<T>`.

    • -0
    • +31
    ./TaskPropertiesIntegrationTest.groovy
  1. … 6 more files in changeset.