On 2010-06-07, SHAILJA wrote:
> /u/kumari/ant> less less build.xml
> <project>
> <target name="install_scripts">
> <copy file="${basedir}/myfile.txt" tofile="/u/kumari/myfile.txt"/>
> <chmod file="/u/kumari/myfile.txt" perm="555"/> </target>
> </project>
> I tried with apache-ant-1.8.1 also and got same error as previous append.
Yes, this is to be expected. More so it will be that way with any later
release of Ant as well. In addition the workaround I suggested will stop
working in the future (but you get a new attribute on <copy> which makes
it overwrite read-only files).
> Stefan Bodewig wrote:
>> For Ant 1.8.0 and 1.8.1 there is a workaround - make <copy> use the
>> filtering mode (i.e. add a filterset that doesn't change your files at
>> all) and it will overwrite read-only files just like 1.7.1 did.
> Can you please suggest me what kind of filter set I can use to copy and
> change mode of this file.
Please note, filtering will break binary files so the advice only
applies to text files. It will not change the mode of any file, it will
just make Ant fall back to the same code that was used in <copy> prior
to Ant 1.8.0 which would happily overwrite read-only files.
What I suggest is something like
<copy file="${basedir}/myfile.txt" tofile="/u/kumari/myfile.txt">
<filterset>
<filter token="foo" value="bar"/>
</filterset>
</copy>
where I assume that myfile.txt does not contain a literal @f...@. With
this approch replacing tokens doesn't change the content of your file
and read-only files can be overwritten in 1.8.[01].
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
