TaskDefinitionIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix TaskDefinitionIntegrationTest

    • -0
    • +2
    ./TaskDefinitionIntegrationTest.groovy
Generate a basic display name for `Property` instances created as the value for a read-only managed property. Use the display name in 'this property has no value' error messages to help with problem diagnosis.

The display name could include some more context, could be used in more error messages, and be applied to more things. This commit is simply an incremental improvement and later changes will improve diagnostics further.

    • -25
    • +0
    ./TaskDefinitionIntegrationTest.groovy
  1. … 23 more files in changeset.
Generate a basic display name for `Property` instances created as the value for a read-only managed property. Use the display name in 'this property has no value' error messages to help with problem diagnosis.

The display name could include some more context, could be used in more error messages, and be applied to more things. This commit is simply an incremental improvement and later changes will improve diagnostics further.

    • -25
    • +0
    ./TaskDefinitionIntegrationTest.groovy
  1. … 23 more files in changeset.
Generate a basic display name for `Property` instances created as the value for a read-only managed property. Use the display name in 'this property has no value' error messages to help with problem diagnosis.

The display name could include some more context, could be used in more error messages, and be applied to more things. This commit is simply an incremental improvement and later changes will improve diagnostics further.

    • -25
    • +0
    ./TaskDefinitionIntegrationTest.groovy
  1. … 25 more files in changeset.
Generate a basic display name for `Property` instances created as the value for a read-only managed property. Use the display name in 'this property has no value' error messages to help with problem diagnosis.

The display name could include some more context, could be used in more error messages, and be applied to more things. This commit is simply an incremental improvement and later changes will improve diagnostics further.

    • -25
    • +0
    ./TaskDefinitionIntegrationTest.groovy
  1. … 23 more files in changeset.
Generate a basic display name for `Property` instances created as the value for a read-only managed property. Use the display name in 'this property has no value' error messages to help with problem diagnosis.

The display name could include some more context, could be used in more error messages, and be applied to more things. This commit is simply an incremental improvement and later changes will improve diagnostics further.

    • -25
    • +0
    ./TaskDefinitionIntegrationTest.groovy
  1. … 25 more files in changeset.
Make deprecations in TaskContainer throw errors

    • -4
    • +3
    ./TaskDefinitionIntegrationTest.groovy
  1. … 14 more files in changeset.
Make deprecations in TaskContainer throw errors

    • -4
    • +3
    ./TaskDefinitionIntegrationTest.groovy
  1. … 14 more files in changeset.
Add an outgoing variants report

This commit introduces an `outgoingVariants` task which generates

a report of the outgoing variants of a project. This is useful

for debugging and understanding variant aware resolution.

It becomes possible for a plugin author to understand what variants

are already produced by a project based on the plugins applied, and

what artifacts are attached to what variant.

    • -1
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 9 more files in changeset.
Add an outgoing variants report

This commit introduces an `outgoingVariants` task which generates

a report of the outgoing variants of a project. This is useful

for debugging and understanding variant aware resolution.

It becomes possible for a plugin author to understand what variants

are already produced by a project based on the plugins applied, and

what artifacts are attached to what variant.

    • -1
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 9 more files in changeset.
Add an outgoing variants report

This commit introduces an `outgoingVariants` task which generates

a report of the outgoing variants of a project. This is useful

for debugging and understanding variant aware resolution.

It becomes possible for a plugin author to understand what variants

are already produced by a project based on the plugins applied, and

what artifacts are attached to what variant.

    • -1
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 9 more files in changeset.
Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

The `TestFixturesPlugin` of our build has been simplified to leverage the native

test fixtures capabilities. Some noticeable changes:

- the `testFixtures` extension has been replaced with regular dependency declaration

- dependencies on test fixtures are now declared using the `testFixtures` keyword

- test fixtures properly declare an API and an implementation, meaning that the

implementation dependencies of test fixtures no longer leak into the compile

classpath of consumers (in particular tests)

    • -3
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 88 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

    • -3
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 84 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

    • -3
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 84 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

    • -3
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 84 more files in changeset.
Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

The `TestFixturesPlugin` of our build has been simplified to leverage the native

test fixtures capabilities. Some noticeable changes:

- the `testFixtures` extension has been replaced with regular dependency declaration

- dependencies on test fixtures are now declared using the `testFixtures` keyword

- test fixtures properly declare an API and an implementation, meaning that the

implementation dependencies of test fixtures no longer leak into the compile

classpath of consumers (in particular tests)

    • -3
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 88 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

    • -3
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 84 more files in changeset.
Fix integ tests after new buit-in task

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -1
    • +3
    ./TaskDefinitionIntegrationTest.groovy
  1. … 3 more files in changeset.
Add some more test coverage for using various `Property` types as task properties.

    • -1
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 4 more files in changeset.
Add some more test coverage for using various `Property` types as task properties.

    • -1
    • +1
    ./TaskDefinitionIntegrationTest.groovy
  1. … 4 more files in changeset.
Add support for read-only properties with type `ConfigurableFileCollection` with an abstract getter on types instantiated by Gradle. Gradle will provide an implementation of the property and (lazily) create a file collection instance as required.

Currently works only in those places where project scope services are visible. This does not include the parameters object for an artifact transform. A subsequent commit will allow this feature to be used in more places.

    • -0
    • +25
    ./TaskDefinitionIntegrationTest.groovy
  1. … 6 more files in changeset.
Add support for read-only properties with type `ConfigurableFileCollection` with an abstract getter on types instantiated by Gradle. Gradle will provide an implementation of the property and (lazily) create a file collection instance as required.

Currently works only in those places where project scope services are visible. This does not include the parameters object for an artifact transform. A subsequent commit will allow this feature to be used in more places.

    • -0
    • +25
    ./TaskDefinitionIntegrationTest.groovy
  1. … 6 more files in changeset.
Improve error reporting when attempting to instantiate an interface or a non-static inner class.

    • -0
    • +24
    ./TaskDefinitionIntegrationTest.groovy
  1. … 9 more files in changeset.
Add some validation of extension constructors, and tweak some error messages.

    • -2
    • +2
    ./TaskDefinitionIntegrationTest.groovy
  1. … 15 more files in changeset.
Add some test coverage of service injection into various types of domain objects.

    • -115
    • +4
    ./TaskDefinitionIntegrationTest.groovy
  1. … 4 more files in changeset.
Move test case from integTest to core project.

    • -0
    • +655
    ./TaskDefinitionIntegrationTest.groovy
  1. … 1 more file in changeset.