Hi all,
I've hit upon what I think are encoding issues with the dependency
and/or resource plugin, and I'd like to sound out what the others' take
on it is.
So imagine a scenario in which one has a module that encapsulates all
web resources (images, css, js, etc ...) which is shared amongst several
webapps. These resources can be packaged in a jar and unpacked via the
dependency plugin in the webapp modules.
The problem that occurs is that building on different platforms (say Mac
for dev and Linux for deployment) the image resources get corrupted (and
cannot be retrieve via the web browser from the deployed webapp).
The reason why I think it's encoding-related is that:
1. Copying the war built on dev machine to server works fine
2. Adopting the workaround of overriding the image resources with the
ones copied from filesystem via ant task (ie by-passing both the
dependency and resource plugins) also works fine when built on the server.
I've tried setting UTF-8 encoding on resources plugin, but that makes
the images unreadable on Mac.
I note in passing that the dependency plugin uses the Plexus Unarchiver
to unpack, but only the ZipUnarchiver allows to set the encoding
property. Is there any reason why setEncoding() is not pulled up to
Unarchiver interface?
Summing up, anybody else experienced similar issues?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
