As of today... by default both stdout/stderr from task are captured
and only displayed if the task is not successful. (capture means the
text is not sent/displayed on the console). You can control the
verbosity from command line using --verbose. where:

0 : (default) capture both stderr/stdout
1 : capture stdout only
2 : dont capture anything

The problem is that different tasks may require a different default level.

Proposed change: add an optional "verbosity" parameter to the task
dictionary. So the the verbosity from a task would be determined by:

1) the explicit verbosity passed from the command line (if any)
2) the verbosity from the task dictionary (if any)
3) the system default

I also think it makes sense to change the system default to 1 (capture
stdout only and print stderr)

it would also be nice to control the verbosity from individual tasks
from command line... but this will have to wait for #370914 - "passing
arguments to tasks on cmd line"
(https://bugs.launchpad.net/bugs/370914)

comments?
volunteers?

take care,
  eduardo

i have created a bug on launchpad for this
https://bugs.launchpad.net/bugs/448518