Hey guys,
One of prominent users describes
a following requirement: the debug logging should end up in a file but
the lifecycle logging (or the current level if configured) should be
visible on the console. The use case that drives that seems to be that
their custom plugin logs some useful stuff at debug level and they
want to get hold of that occasionally without requiring the developer
to rerun the build with --debug.
In general, the idea like that makes sense to me. Many times I had to
rerun the build with --debug but I couldn't reproduce some
misbehavior. Or the build was long enough to make the re-run
inconvenient and frustrating. Hence I always wanted gradle to
automatically keep the --debug level logs somewhere for a couple of
past builds.
One way to achieve that would be configuring appenders of Gradle
logging. However, I don't think this is possible (or I couldn't manage
to do it from a custom plugin).
My current understanding is:
1. it's not possible to implement something that in a custom plugin,
not even via any private api. (please correct me if I'm wrong :)
2. the only workaround (with obvious downsides) that I can think of is
rolling own logging in the custom plugin that writes to a file (or
using a logging tooling Gradle does not capture).
If you have some feedback, please share.
Cheers
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
