Hans Dockter wrote:
Hi,
right now we have an output like the following:
================================================ Start building buildSrc
Executing Task: :clean
Executing Task: :init
Executing Task: :resources
Executing Task: :compile
Executing Task: :testResources
Executing Task: :testCompile
Executing Task: :test
Executing Task: :archive_jar
Executing Task: :libs
Executing Task: :uploadInternalLibs
================================================ Finished building
buildSrc
Executing Task: :clean
Executing Task: :shared:clean
Executing Task: :api:clean
Executing Task: :services:clean
Executing Task: :services:webapp1:clean
BUILD SUCCESSFUL
Total time: 3.038 secs
I'm wondering if we should turn it into:
Building build sources ...
root
[clean]
Some task output
shared
[clean]
api
[clean]
services
[clean]
services:webapp1
[clean]
BUILD SUCCESSFUL
Total time: 3.038 secs
We could certainly lose the 'Executing Task' bit, it doesn't carry any
real useful information. And make the build source announcements less
prominent.
I'm not sure that treating project as the top level grouping will work
that well, as Gradle bounces around quite a bit between projects if you
have a few projects with a deep task graph. We could certainly change
things so that Gradle attempts to group dependencies by project as it
executes them. Then this kind of output scheme could make sense, and it
would probably make the execution order appear less random than it does
(I know it's entirely deterministic, but it feels random you get when
you watch it execute).
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
