Lines Matching refs:archives

176 o Expanding 7z archives using LZMA compression could cause an
179 o Long-Name and -link or PAX-header entries in TAR archives always had
180   the current time as last modfication time, creating archives that
210 o COMPRESS-278:  TarArchiveInputStream failed to read archives with empty
241   You will need a version >= 1.5 of XZ for Java to read archives
250   archives used LZMA compression for headers and content and
256 o TarArchiveInputStream will now read archives created by tar
308 o SevenZOutputFile would create invalid archives if more than six
324 o Added support for 7z archives.  Most compression algorithms
327 o Added read-only support for ARJ archives that don't use
340   to be able to read archives created by DotNetZip and maybe
350 o CpioArchiveInputStream failed to read archives created by
437 o Split/spanned ZIP archives are now properly detected by
440 o ZipArchiveInputStream now reads archives that start with a "PK00"
467 o ZipFile's initialization has been improved for non-Zip64 archives.
495                  The stream classes now write (or expect to read) archives that
507                  short text files were TAR archives. 
508 o COMPRESS-164:  ZipFile didn't work properly for archives using unicode extra
510 o COMPRESS-169:  For corrupt archives ZipFile would throw a RuntimeException in
515 o COMPRESS-182:  The tar package can now write archives that use star/GNU/BSD
527 o COMPRESS-16:  The tar package can now read archives that use star/GNU/BSD
529                  archives that use the POSIX/PAX variant. 
530 o COMPRESS-165:  The tar package can now write archives that use star/GNU/BSD
532                  archives that use the POSIX/PAX variant. 
624         The method currently returns false for ZIP archives if an
647 o COMPRESS-101:  ZipArchiveInputStream should now properly read archives that
653         number of bytes read for big archives. 
654 o COMPRESS-85:  The cpio archives created by CpioArchiveOutputStream couldn't
656         archives contained multiple entries with the same inode/device
663         archives cannot be parsed. 
667         archives if two different entries had the same hash code. Thanks to Anon Devs.