Releases: Col-E/LL-Java-Zip
Releases · Col-E/LL-Java-Zip
Release 2.3.0
Changelog
- 93f5065 Allow toggling of skipping N-to-1 CEN-to-LOC entry mapping in JvmZipReader, defaulting to true
- a31ea49 Create zip reader impl delegating to java.util.zip.ZipFile
- 83a6add Create no-op byte data impl
- d601ec2 Fix initial jvmBaseFileOffset value for scanning for LOC entries being 0 when it should be > 0 in some cases
- 620c84d Fix error message not propagating in decompressors
Contributors
- @1fxe for noting the behavior difference between
ZipFile
andJvmZipReader
Release 2.2.0
Changelog
- 0119973 Expose extra-field time extraction utility logic
Release 2.1.4
Changelog
- edf65fe Do not overwrite extra-field for JVM handling of LocalFileHeader when copying from CentralDirectoryFileHeader
Release 2.1.3
Changelog
🔀 Merge
- d95ffa1 Make jvm strategy not go beyond the END header's given directory offset
- bfc7054 Yet another ByteBuffer related java 1.8 bug
Contributors
We'd like to thank the following people for their contributions:
- KosmX
- Ned Loynd (@NeRdTheNed)
Release 2.1.2
Release 2.1.1
Changelog
- New samples from #22 - Fixes for issues discovered by analyzing samples:
Contributors
We'd like to thank the following people for their contributions:
- Ned Loynd (@NeRdTheNed)
- Col-E
Release 2.1.0
Changelog
- 2b6beef Allow zip part mappers to drop entries
Release 2.0.0
The sonatype staging server timed out when replying, but it seems like it still got the release since I got emailed the security scan passed 💀
Sadly this prevented the automated github release. So here I am manually making this.
Changelog
- #20 A number of refactoring changes
- Renamed
llzip
tolljzip
packages to match the artifact id - Renamed
Strategy
interfaces to remove the suffix - New utilities for manipulating
ZipArchive
instances ZipPart
types now have copy operations
- Renamed
- #19 The JVM reader strategy/local-header now considers data-descriptors when computing the data section size
Contributors
- NeRdTheNed
- Col-E
Release 1.6.1
Changelog
- 0cd4498 Sadly, those two putBoolean calls are required. Due to API stability across versions, UnsafeInflater is replaced with InflaterHackery, which instead just calls the appropriate methods instead of updating fields
Contributors
We'd like to thank the following people for their contributions:
- xxDark
- Col-E