That's a reasonable explanation, I suppose, but
does Java even have the notion of opening a file
in binary or text mode? Wonder if the native impls
are consistent in this regard.
Keith
| -----Original Message-----
| From: Jon Skeet [mailto:jon.skeet@peramon.com]
| Sent: Wednesday, June 12, 2002 4:45 PM
| To: Ant Developers List
| Subject: RE: filter copy corrupts jars?
|
|
| > I ran into a problem that I don't have time to diagnose
| > more thoroughly, but perhaps someone with more knowledge
| > of the filter code can help.
| >
| > In a copy with multiple filtersets, a jar that doesn't match
| > any tokens is corrupted. I verified no matches by running
| > with the verbose flag; I saw matches in text files, but no
| > matches for the jar. In a copy with no filtersets, the
| > copied jar is fine.
| >
| > Is it at all conceivable that the file is being modified,
| > even if a token match is not reported by -v?
|
| Unless I'm just tired, you should *never* copy any binary files with filtering turned on.
Even if it doesn't match any
| tokens, it's still reading and writing as if it's text.
|
| As I say, I could be wrong...
|
| Jon
|
| --
| To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
| For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
|
|
--
To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
|