One thing to keep in mind, less is not more for some people. Grails 2, inspired by Gradle, got much more concise when it came to its console output. This is generally ok, but is already proving problematic when things go wrong. I don't have an answer here, but one thing we need to make sure of is that people can readily understand what's happening. That's ultimately more important than conciseness.
On 04/11/2011, at 7:58 AM, Hans Dockter wrote: > I would like to see a reduced console output in Gradle. Thanke to our dynamic > output we don't need to abuse the actual logging anymore to be a progress bar. > > Why not do the following by default: Show only the root tasks per project > that were executed. For example > > Singe Project Build: > gradle build > :build > > gradle clean test > :clean: > :test > > Multiproject Project Build in foo(foo depends on bar): > > gradle build > :bar:jar > :foo:build > > gradle buildDependent > :bar:build > :foo:build > > This would avoid in particular the clutter of using buildSrc. Of course if > you have no console than enables dynamic output we should switch back to our > current way of logging. > > One challenge I see with implementing this is the order in which thing are > displayed in a multiproject build. Right now we have: > > ... > :bar:jar > ... > :foo:build > ... > :bar:build > > But to only show the following in that order would be confusing: > > foo:build > bar:build > > As the dependencies between foo and bar are the opposite. > > Hans > -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
