Hans Dockter wrote:
Hi,
I have submitted some work to make the default logging less noisy in
the future. What it does is to catch all Ivy and Ant output and
delegate it to slf4j. There is now also a slf4j marker called
HIGH_LEVEL. Any logging statement having this marker is supposed to be
shown by default on the console. There is one problem left to solve.
The Groovy compile is happening in its own classloader (to enable
using a different Groovy version for Gradle Groovy projects than the
one shipped with Gradle). We have to rearrange things that this
compile is also using the same loggers.
Beside this there is one usability question. On the console we will
have a minimized output. Should we write the current verbose console
output to a file by default?
Probably. Which file would it go to? $rootDir/.gradle/gradle.log,
$rootDir/gradle.log or $rootDir/build/gradle.log seem like good options
to me.
We'd need a command-line option to override this, and it also seems like
something you'd want to override in your gradle init file.
Something I'd like is the ability to control from the command-line the
logging levels for broad functional areas, such as the projects, ant,
ivy, groovy and gradle itself. We have this for ivy already, it would be
nice to generalise this a bit. For example, gradle -d ivy -d ant would
enable debug level for all ivy and ant logging. Or gradle -d projects
would enable debug level for my project's logging.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
