Mauro Talevi wrote:
ZipUnarchiver.setEncoding() only controls the encoding for file names
as given by zip entries [1,2], not the encoding of the compressed file
contents [3]. So unless you experience corrupt file names, that
shouldn't be the cause of your problem.
Ok - understood, but shouldn't the copying done via the unarchiver in
the dependency plugin be able to set the encoding like the resource plugin?
What encoding exactly would you like to set? The encoding of the file
contents? This is not necessary. Encoding is only required when one has
to convert between bytes and characters but the (un-)archiving of files
is merely a byte-to-byte copy, i.e. operates on a lower level and does
not involve textual interpretation of the file contents:
Characters --filter--> Characters Semantic Layer
^ |
| |
decode encode
| |
| v
Bytes ---copy---> Bytes Physical Layer
IIRC, the Dependency Plugin doesn't do filtering so should be fine
without encoding configuration.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
