Ordering of tasks clean and build in Gradle 1.7?


(dinio.dinev) #1

I apply java plugin in my project and when I execute

gradle clean build
-m

I have

:clean SKIPPED
:compileJava SKIPPED
:processResources SKIPPED
:classes SKIPPED
:jar SKIPPED
:assemble SKIPPED
:compileTestJava SKIPPED
:processTestResources SKIPPED
:testClasses SKIPPED
:test SKIPPED
:check SKIPPED
:build SKIPPED

but when I change the order of clean and build

gradle build
clean -m

I have

:compileJava SKIPPED
:processResources SKIPPED
:classes SKIPPED
:jar SKIPPED
:assemble SKIPPED
:compileTestJava SKIPPED
:processTestResources SKIPPED
:testClasses SKIPPED
:test SKIPPED
:check SKIPPED
:build SKIPPED
:clean SKIPPED

Why this happen?


(René Groeschke) #2

When invoking multiple tasks via commandline, gradle maintains the order you typed as long as there are not task dependencies declared between those tasks which contradict the commandline order. in that case, the task dependency order is used.

cheers, René


(dinio.dinev) #3

OO there is no dependency between clean and build tasks and thus Gradle uses the order we typed. Thanks