Gradle Goodness: Run Tasks Ignoring Up-to-Date Checks [Code Snippet]
Gradle Goodness: Run Tasks Ignoring Up-to-Date Checks [Code Snippet]
You can use Gradle for builds for incremental tasks, building only when things change. This quick code snippet introduces the assemble and rerun task commands
Join the DZone community and get the full member experience.
Join For FreeAtomist automates your software deliver experience. It's how modern teams deliver modern software.
Gradle builds are fast because Gradle supports incremental tasks. This means Gradle can determine if input or output of tasks has changed — before running the task. If nothing has changed, a task is marked as up-to-date and the task is not executed. Otherwise, the task is executed. If we want to execute a task even if it is up-to-date we must use the command line option --rerun-tasks.
In the following example, we run the assemble task for a simple Java project, and we see all tasks are executed. When we invoke the assemble task again we see the tasks are all up-to-date:
$ gradle assemble :compileJava :processResources :classes :jar :assemble
BUILD SUCCESSFUL Total time: 1.765 secs
$ gradle assemble
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar UP-TO-DATE
:assemble UP-TO-DATE BUILD SUCCESSFUL
Total time: 0.715 secs
$ To run all tasks without an up-to-date check we use the option --rerun-tasks:
Written with Gradle 3.2.1.
Get the open source Atomist Software Delivery Machine and start automating your delivery right there on your own laptop, today!
Like This Article? Read More From DZone
Published at DZone with permission of Hubert Klein Ikkink , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}