Hi Kristian,
On 10/10/14 12:16 PM, Kristian Rosenvold wrote:
No. It is platform encoding dependent. Which is why we have a bunch of
issues in maven-assembly-plugin about this behaviour.
Ok...so i think this issue http://jira.codehaus.org/browse/MJAR-135 is
related to this behaviour as well....Hm...may be more related to
directory name encoding ..?
Can we create a jira issue in PLXCOMP so i can link also the issues
related to this...
The JAR archiver does this already, since its part of the jar spec.
You mean jar on command line ?
Kristian
2014-10-10 11:58 GMT+02:00 Karl Heinz Marbaise <khmarba...@gmx.de>:
Hi Kristina,
just a question on this topic...does currently jar from plexus-archiver
already behave like this and uses UTF-8 encoding always ? Or is this
platform dependent?
On 10/10/14 8:26 AM, Kristian Rosenvold wrote:
Currently plexus-archiver uses platform encoding for zip file names if
none is specified. This is "compliant" with traditional Zip history.
But zip understood this is a problem and introduced a "LEF" flag,
which basically means all entries must be UTF-8.
I would like to switch defaults in plexus zip archiver; make it
*disregard* platform encoding and always output utf8 + LEF, unless a
different encoding has been explicitly specified.
In consequence this would make zip behave like "jar" does; always
default to the well-defined UTF-8 + LEF standard.
This will break builds for people that actually *want* archives in
file.encoding; they will need to explicitly specify encoding to get
that encoding. To my understanding this is not really an issue, LEF
support is ancient history.
Opinions ?
Kristian
Kind rergards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
