On Tue, 2008-11-04 at 16:31 +1100, Adam Murdoch wrote: > > 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
The above just gives feedback as to where the build has got to. It is lightweight, a clean output and does the job of being an indicator to the user that things are progressing. > > 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 Is this from a different build to the previous one? I can't see how the phases of the build map from this one to the previous one. As a personal note, I find Maven far too verbose normally and having to type mvn -q a real pain. > We could certainly lose the 'Executing Task' bit, it doesn't carry any > real useful information. And make the build source announcements less > prominent. As long as there is something to show where the build has got to and what it might be doing then any lightweight output is fine. > 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). I'll have to pass on this, I only have very simple projects :-) -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
