Hans Dockter wrote:
On Sep 22, 2008, at 10:46 PM, Hans Dockter wrote:
On Sep 22, 2008, at 10:20 PM, Adam Murdoch wrote:
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.
I'm not sure. The gradle.log in the top level dir would have the
advantage that people would learn simply from using Gradle that there
is such a file. On the other hand it pollutes the top level dir which
is something many people feel rather sensitive about.
I forgot to say: I hadn't thought about putting it in the build dir
yet. But I think that would be the best location.
Thinking about it, one problem with putting the log file in the build
dir is that we don't know where the build dir is until after the
settings have been built, which is quite a way into the initialisation.
We'd either have to buffer or discard log messages until after the
settings have been built.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
