Browse Source
More warnings about filtering binary files. Bugzilla #39445.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@397909 13f79535-47bb-0310-9956-ffa450edef68master
Matthew Jason Benson
19 years ago
2 changed files with 9 additions and 7 deletions
Unified View
Diff Options
+ 3
- 2
docs/manual/CoreTasks/filter.html
View File
| @@ -13,7 +13,8 @@ | |||||
| <p>Sets a token filter for this project or read multiple token filter from | <p>Sets a token filter for this project or read multiple token filter from | ||||
| an input file and sets these as filters. | an input file and sets these as filters. | ||||
| Token filters are used by all tasks that perform file copying operations | Token filters are used by all tasks that perform file copying operations | ||||
| through the Project commodity methods.</p> | |||||
| through the Project commodity methods. See the warning | |||||
| <a href="../using.html#filters"><em>here</em></a> before using.</p> | |||||
| <p>Note 1: the token string must not contain the separators chars (@).<br> | <p>Note 1: the token string must not contain the separators chars (@).<br> | ||||
| Note 2: Either token and value attributes must be provided, or only the | Note 2: Either token and value attributes must be provided, or only the | ||||
| filtersfile attribute.</p> | filtersfile attribute.</p> | ||||
| @@ -56,7 +57,7 @@ will read all property entries from the <i>deploy_env.properties</i> file | |||||
| and set these as filters. | and set these as filters. | ||||
| <hr> | <hr> | ||||
| <p align="center">Copyright © 2000-2002,2004-2005 The Apache Software Foundation. All rights | |||||
| <p align="center">Copyright © 2000-2002, 2004-2006 The Apache Software Foundation. All rights | |||||
| Reserved.</p> | Reserved.</p> | ||||
| </body> | </body> | ||||
+ 6
- 5
docs/manual/CoreTypes/filterchain.html
View File
| @@ -9,10 +9,11 @@ | |||||
| <body> | <body> | ||||
| <h2>FilterChains and FilterReaders</h2> | <h2>FilterChains and FilterReaders</h2> | ||||
| Look at Unix pipes - they offer you so much flexibility - | |||||
| say you wanted to copy just those lines that contained the | |||||
| string blee from the first 10 lines of a file 'foo' | |||||
| to a file 'bar' - you would do something like<p> | |||||
| Consider the flexibility of Unix pipes. If you wanted, | |||||
| for example, to copy just those lines that contained the | |||||
| string blee from the first 10 lines of a text file 'foo' | |||||
| (<em>you wouldn't want to filter a binary file</em>) | |||||
| to a file 'bar', you would do something like:<p> | |||||
| <code> | <code> | ||||
| cat foo|head -n10|grep blee > bar | cat foo|head -n10|grep blee > bar | ||||
| </code><p> | </code><p> | ||||
| @@ -1402,4 +1403,4 @@ This may be used as follows: | |||||
| <hr> | <hr> | ||||
| <p align=center>Copyright © 2002-2006 The Apache Software Foundation. All rights | <p align=center>Copyright © 2002-2006 The Apache Software Foundation. All rights | ||||
| Reserved.</p></body></html> | |||||
| Reserved.</p></body></html> | |||||