Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
To: ant-user@jakarta.apache.org
Subject: Re: Logging javac error output
References: <H000046e0c76f2fe@MHS>
From: Stefan Bodewig <bodewig@bost.de>
Date: 19 Oct 2000 11:40:22 +0200
In-Reply-To: r.merkle@siep.shell.com's message of "Thu,
 19 Oct 2000 09:59:47 +0200"
Message-ID: <m31yxd6uex.fsf@sbodewig.bost.de>
Lines: 23
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

>>>>> "rm" == r merkle <r.merkle@siep.shell.com> writes:

 rm> A workaround appears to be using: <property name="build.compiler"
 rm> value="classic"/> Then the messages are correct and logged
 rm> correctly to the logfile.

This one finally pushed me into the right direction.

When doing a "classic" compile, Ant hands the compiler a OutputStream
to write its messages to (sun.tools.javac.Main has a constructor
taking an OutputStream argument).

Unfortunately this functionality (writing to a user supplied stream)
doesn't exist in the modern compiler, at least a quick reflection test
of all constructors and methods of com.sun.tools.javac.Main doesn't
provide anything useful.

The only workaround I see is to change System.err and System.out prior
to invoking the compiler and resetting it afterwards, but maybe
somebody with access to the source of the modern compiler knows a
better way to achieve this?

Stefan