You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2001/07/18 20:20:14 UTC
[Bug 2672] - filter/copy tasks will change files even if no filter tokens replaced
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2672
*** shadow/2672 Wed Jul 18 09:06:06 2001
--- shadow/2672.tmp.11349 Wed Jul 18 11:20:13 2001
***************
*** 2,9 ****
| filter/copy tasks will change files even if no filter tokens replaced |
+----------------------------------------------------------------------------+
| Bug #: 2672 Product: Ant |
! | Status: NEW Version: 1.3 |
! | Resolution: Platform: PC |
| Severity: Major OS/Version: Windows NT/2K |
| Priority: Other Component: Core tasks |
+----------------------------------------------------------------------------+
--- 2,9 ----
| filter/copy tasks will change files even if no filter tokens replaced |
+----------------------------------------------------------------------------+
| Bug #: 2672 Product: Ant |
! | Status: RESOLVED Version: 1.3 |
! | Resolution: INVALID Platform: PC |
| Severity: Major OS/Version: Windows NT/2K |
| Priority: Other Component: Core tasks |
+----------------------------------------------------------------------------+
***************
*** 25,28 ****
or contentType="application/x-java-serialized-object")
The expected correct behaviour would be the file completely unchanged, if no
! replacements have been applied.
--- 25,38 ----
or contentType="application/x-java-serialized-object")
The expected correct behaviour would be the file completely unchanged, if no
! replacements have been applied.
!
! ------- Additional Comments From glennm@apache.org 2001-07-18 11:20 -------
! The filter task is not intended for use with binary files; exclude these files
! from your filtered copy.
!
! As far as line endings go, this is a platform issue. If the file was written on
! a Windows machine with CRLF endings and is filtered on a *nix machine, the line
! endings will now be LF. This is a side effect of using the
! BufferedWriter.newLine() method. If you have this situation, use the FixCRLF
! task to clean up your files.