Note that a finalizer is not guaranteed to run, so the feature was not 100% effective in any case. The code will need to be changed to call finish or close itself. This is going to break code that relied on the finalizer to clean up an unfinished stream. Release 1.12 changes the behavior of BZip2CompressorOutputStream's finalize method so that it no longer invokes finish. Release 1.12 - API compatible to 1.11 but requires Java 6 at runtime. Release 1.13 - API compatible to 1.12 but requires Java 7 at runtime. This may break compatibility for code that deliberately wanted to create such files. Release 1.15 - TarArchiveOutputStream now ensures record size is 512 and block size is a multiple of 512 as any other value would create invalid tar archives. Release 1.18 - This release changes the OSGi Manifest entry Bundle-SymbolicName from to -compress. There is no practical difference when they are read via ZipArchiveInputStream or ZipFile.
Some of the ZIP extra fields related to strong encryption will now throw ZipExceptions rather than ArrayIndexOutOfBoundsExceptions in certain cases when used directly.
You can influence the way extra fields are parsed in more detail by using the new getExtraFields(ExtraFieldParsingBehavior) method of ZipArchiveEntry now. Release 1.19 - ZipArchiveInputStream and ZipFile will no longer throw an exception if an extra field generally understood by Commons Compress is malformed but rather turn them into UnrecognizedExtraField instances. This is a breaking change if you relied on the recovery attempt. Release 1.21 (Java 8) - SevenZFileOptions has a new setting that needs to be enabled explicity if SevenZFile should try to recover broken archives - a feature introduced with Commons Compress 1.19. Apache Commons Compress Release Notes Release History Version
0 kommentar(er)
