ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilbert Rebhan <>
Subject ant 1.7.1 bug in <record> with antcall !?
Date Tue, 09 Jun 2009 19:48:18 GMT


after (finally) upgrading from ant 1.6.5 to ant 1.7.1 a teammate
discovered some strange behaviour =

He makes heavy use of antcall and uses the <record> task.
Now with ant 1.7.1 there are a lot of 0 byte lines in the logs,
his editor jumps automatically in hexmode when opening
such a logfile.

Compared to ant 1.6.5 several parts of the logs are missing - probably
overwritten by those 0 byte lines.
Whether heavy use of antcall is good or bad style, that behaviour of
<record> task in ant 1.7.1 is _very annoying_, as important parts of the
logs are missing now after the upgrade.

There was already a similar posting on the ant user list =
but got no repsone.

So, is that a known bug among other users|developers, didn't find a
record in the bug database ?
Maybe it's already patched in repository !?
Any suggestions or workarounds ??

Regards, Gilbert

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message