ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grimm, Markus" <>
Subject AW: ant 1.7.1 bug in <record> with antcall !?
Date Wed, 10 Jun 2009 06:11:31 GMT
Hi Gilbert,

at that time I found a workaround for my problem at

If we look at the same sample script, so you have to open the log-file in the first target,
that is
executed and close it in the last target:

<?xml version="1.0" encoding="UTF-8"?>
<project name="test" default="main" basedir=".">

	<target name="main" depends="t1,t2">
		<echo message="main-target" />

	<target name="t1" depends="t2">
		<echo message="I'm in t1 an call t3" />
		<antcall target="t3" />

	<target name="t2">
		<record action="start" append="yes" name="test.log" />
		<echo message="t2-target is executed" />

	<target name="t3">
		<echo message="t3-target is executed" />
		<record action="stop" name="test.log" />

Now it works!
Hope that helps...

I don't know if it's a bug or feature.
Recently I was reading an article about announcing bugs in open source projects.
Many people criticize that bugs won't be fixed but scarcely anybody opens a bug. So it can't
be fixed.
On the other side it's important for me, that the community gives a feedback about an issue,
so you can be
sure not to put some bullshit in the bugtracker ... 


-----Urspr√ľngliche Nachricht-----
Von: Gilbert Rebhan [] 
Gesendet: Dienstag, 9. Juni 2009 21:48
An: Ant Users List; Ant Developers List
Betreff: ant 1.7.1 bug in <record> with antcall !?


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:

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

View raw message