Gradle Incremental Builds - Declaring Inputs and Outputs with Runtime API: Difference between revisions
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
Annotations in custom task types are the cleanest way to declare inputs and outputs. However, simple tasks can be configured to participate in incremental builds by using the Runtime API. There is also the case of the enhanced tasks we don't have source code for. In all these situations, we can configure the task's inputs and outputs with an alternative runtime API: | Annotations in custom task types are the cleanest way to declare inputs and outputs. However, simple tasks can be configured to participate in incremental builds by using the Runtime API. There is also the case of the enhanced tasks we don't have source code for. In all these situations, we can configure the task's inputs and outputs with an alternative runtime API: | ||
[https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:inputs Task.getInputs()] | [https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:inputs Task.getInputs()] | ||
[https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:outputs Task.getOutputs()] | [https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:outputs Task.getOutputs()] | ||
[https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:destroyables Task.getDestroyables()] | [https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:destroyables Task.getDestroyables()] | ||
These objects have methods that allow specifying files, directories and values. The API is almost at parity with the annotations, it is only missing @Nested. | The methods return [https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/TaskInputs.html TaskInputs], [https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/TaskOutputs.html TaskOutputs] and [https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/TaskDestroyables.html TaskDestroyables] instances. These objects have methods that allow specifying files, directories and values. The API is almost at parity with the annotations, it is only missing [[Gradle_Incremental_Builds#Nested_Values|@Nested]]. |
Revision as of 03:54, 22 October 2020
External
Internal
Overview
Annotations in custom task types are the cleanest way to declare inputs and outputs. However, simple tasks can be configured to participate in incremental builds by using the Runtime API. There is also the case of the enhanced tasks we don't have source code for. In all these situations, we can configure the task's inputs and outputs with an alternative runtime API:
Task.getInputs() Task.getOutputs() Task.getDestroyables()
The methods return TaskInputs, TaskOutputs and TaskDestroyables instances. These objects have methods that allow specifying files, directories and values. The API is almost at parity with the annotations, it is only missing @Nested.