You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Gilbert Rebhan <an...@schillbaer.de> on 2009/06/09 21:48:18 UTC
ant 1.7.1 bug in with antcall !?
Hi,
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 =
http://marc.info/?l=ant-user&m=123900769210029&w=2
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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
AW: AW: ant 1.7.1 bug in with antcall !?
Posted by "Grimm, Markus" <Gr...@juris.de>.
Hi Gilbert,
I think this could be the appropriate issue in the bug database:
https://issues.apache.org/bugzilla/show_bug.cgi?id=41368
So it doesn't seem to be fixed in the current ant release ?!
But there's a patch to fix the problem, too ...
Thanks,
Markus
-----Ursprüngliche Nachricht-----
Von: Gilbert Rebhan [mailto:ant@schillbaer.de]
Gesendet: Mittwoch, 10. Juni 2009 22:07
An: Ant Users List
Betreff: Re: AW: ant 1.7.1 bug in <record> with antcall !?
Hi Markus,
Grimm, Markus schrieb:
> Hi Gilbert,
>
> at that time I found a workaround for my problem at
> http://marc.info/?l=ant-user&m=123900769210029&w=2
>
> 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:
[...]
>
> Now it works!
> Hope that helps...
thanks for your response, the workmate changed his scripts like that :
before with ant 1.6.5 =
<record .... action=start append=true"/>
<antcall>
<copy> of the log to ../logs/someotherfilename.log
<antcall>
<copy> of the log to ../logs/someotherfilename.log
... etc.
so he never called <record action="stop"/> to have the output from
<copy> also into the logfile
now after the problems when upgrading to ant 1.7.1, he tried :
<record .... action=start append=true">
<antcall>
<record ... action=stop append=true/>
<copy> of the log to ../logs/someotherfilename.log
<antcall>
<record ... action=stop append=true/>
<copy> of the log to ../logs/someotherfilename.log
... etc.
and now it works for him, but only if he uses <record action=stop
with append=true> , means <record action=stop> doesn't work and gives
an empty logilfe.
Regards, Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: AW: ant 1.7.1 bug in with antcall !?
Posted by Gilbert Rebhan <an...@schillbaer.de>.
Hi Markus,
Grimm, Markus schrieb:
> Hi Gilbert,
>
> at that time I found a workaround for my problem at
> http://marc.info/?l=ant-user&m=123900769210029&w=2
>
> 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:
[...]
>
> Now it works!
> Hope that helps...
thanks for your response, the workmate changed his scripts like that :
before with ant 1.6.5 =
<record .... action=start append=true"/>
<antcall>
<copy> of the log to ../logs/someotherfilename.log
<antcall>
<copy> of the log to ../logs/someotherfilename.log
... etc.
so he never called <record action="stop"/> to have the output from
<copy> also into the logfile
now after the problems when upgrading to ant 1.7.1, he tried :
<record .... action=start append=true">
<antcall>
<record ... action=stop append=true/>
<copy> of the log to ../logs/someotherfilename.log
<antcall>
<record ... action=stop append=true/>
<copy> of the log to ../logs/someotherfilename.log
... etc.
and now it works for him, but only if he uses <record action=stop
with append=true> , means <record action=stop> doesn't work and gives
an empty logilfe.
Regards, Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
AW: ant 1.7.1 bug in with antcall !?
Posted by "Grimm, Markus" <Gr...@juris.de>.
Hi Gilbert,
at that time I found a workaround for my problem at
http://marc.info/?l=ant-user&m=123900769210029&w=2
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>
<target name="t1" depends="t2">
<echo message="I'm in t1 an call t3" />
<antcall target="t3" />
</target>
<target name="t2">
<record action="start" append="yes" name="test.log" />
<echo message="t2-target is executed" />
</target>
<target name="t3">
<echo message="t3-target is executed" />
<record action="stop" name="test.log" />
</target>
</project>
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 ...
Thanks,
Markus
-----Ursprüngliche Nachricht-----
Von: Gilbert Rebhan [mailto:ant@schillbaer.de]
Gesendet: Dienstag, 9. Juni 2009 21:48
An: Ant Users List; Ant Developers List
Betreff: ant 1.7.1 bug in <record> with antcall !?
Hi,
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 =
http://marc.info/?l=ant-user&m=123900769210029&w=2
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: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org