On 2011-08-11, Emmanuel Bourg wrote:
> Le 01/08/2011 16:49, Stefan Bodewig a écrit :
>> All other archives are read correctly by ZipArchiveInputStream, there is
>> a problem with reading the size of the big entry inside the archive
>> created by jar, but this clearly is a bug in Java7 and I'm goi
Le 01/08/2011 16:49, Stefan Bodewig a écrit :
All other archives are read correctly by ZipArchiveInputStream, there is
a problem with reading the size of the big entry inside the archive
created by jar, but this clearly is a bug in Java7 and I'm going to
report it against OpenJDK[1] (and may hav
Stefan Bodewig wrote:
> On 2011-08-01, Jörg Schaible wrote:
>
>> Stefan Bodewig wrote:
>
>> [snip]
>
>>> [1] Once I manage to set finalize the account creation process at the
>>> bug database, that is. Do they really think I'd give them my business
>>> phone number and street address in order
On 2011-08-01, Jörg Schaible wrote:
> Stefan Bodewig wrote:
> [snip]
>> [1] Once I manage to set finalize the account creation process at the
>> bug database, that is. Do they really think I'd give them my business
>> phone number and street address in order to report a bug?
> I always do:
> +
Stefan Bodewig wrote:
[snip]
> [1] Once I manage to set finalize the account creation process at the
> bug database, that is. Do they really think I'd give them my business
> phone number and street address in order to report a bug?
I always do:
+00042-4200420042
42/0 Lunar City, Moon
SCNR :
Hi,
I've checked current trunk's ZipArchiveInputStream and
ZipArchiveOutputStream implementations against InfoZIP's zip (Cygwin in
this case), 7ZIP, windows Compressed Folders and Oracle's final Java7
JDK's jar command - all on Windows 7.
For InputStream I've created an archive with a single comp
