On Sep 24, 2008, at 10:53 AM, Adam Murdoch wrote:
Hans Dockter wrote:
Hi,
some Ant tasks don't use the Ant logging system for some of there
messages but use System.out.println instead. For example the javac
tasks does this with warnings from the compiler. The launch4j
tasks does this as well. There is not much we can do about this as
long as we use those tasks.
We would still have this problem if builds do their own writing to
stdout, or if they fork processes, or if they use these ant tasks
(or ones like them) directly.
To solve the problem, we could bridge stdout and stderr across to
logging, with default info level for stdout and error level for
stderr.
Good point. I gonna implement a STDOUT/ERR logging adapter.
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
