On Wed, Jul 14, 2010 at 17:39, Adam Murdoch <[email protected]> wrote: > On 14/07/10 9:56 PM, Hans Dockter wrote: >> >> Hi, >> >> I'm wondering if we ever had a use case for >> Task.disableStandardOutputCapture() and whether we should deprecate this >> method. > > We should do the same for Project.disableStandardOutputCapture() and > Script.disableStandardOutputCapture(). > > Also, we should think about deprecating captureStandardOutput() on Task, > Project and Script, and replacing it with > LoggingManager.captureStandardOutput(). Each of these things already > delegates to a LoggingManager, so we could easily add a getLogging() method > to expose the LoggingManager. > > This way, we can add more logging configuration methods to LoggingManager > and they are available from each of these places (plus any more such > 'executable' things that we might add later). Plus it moves the logging > config methods to their own namespace, which feels much better.
+1 Feels like a good refactor > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > CTO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
