Running with -a doesn't work


(Jesper Thuun-Petersen) #1

I’m having trouble with the -a option. It doesn’t seem to have any effect, that is, all dependend modules are compiled no matter what.

Here’s a snippet from the log, running without the option:

All projects evaluated. Selected primary

task ‘integrationendpointplugins:test’ Tasks to be executed: [task ‘:framework:compileJava’,

task ‘:framework:copyExternalDependencies’,

task ‘:framework:generateRebel’,

task ‘:framework:processResources’,

task ‘:framework:classes’,

task ‘:framework:publicAPIJar’,

task ‘:framework:publicAPIJavadoc’,

task ‘:framework:bndTask’,

task ‘:framework:jar’,

task ‘:framework:compileTestJava’,

task ‘:framework:processTestResources’,

task ‘:framework:testClasses’,

I now add the -a option, and here’s the same part of the log:

All projects evaluated. Selected primary

task ‘integrationendpointplugins:test’ Tasks to be executed: [task ‘:framework:compileJava’,

task ‘:framework:copyExternalDependencies’,

task ‘:framework:generateRebel’,

task ‘:framework:processResources’,

task ‘:framework:classes’,

task ‘:framework:compileTestJava’,

task ‘:framework:processTestResources’,

task ‘:framework:testClasses’,

The integrationendpointplugins depends on the module framework. I would have thought the -a option would remove all tasks not related to the module I’m running in, but apparently, this is not the case. It does remove a couple of tasks, but I can’t seem to find a pattern to why it has removed these tasks, and not the rest?!

I’m running gradle 1.4 and java 7.

Regards /Jesper Thuun-Petersen