[
https://issues.apache.org/jira/browse/COMPRESS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286233#comment-16286233
]
Stefan Bodewig commented on COMPRESS-420:
-----------------------------------------
I guess I need to find some time to play with your archive again.
If COMPRESS-367 is the change then you'd get an exception where
{{getNextExntry}} used to return {{null}} - in either case reading would end
here. If you are now seeing the exception in a place where the method used to
return something else, then it must be a different change.
Under the assumption COMPRESS-367 introduced what you are seeing the stream
simply is positioned in a place where {{ZipArchveInputStream}} cannot proceed.
Having a callback wouldn't help here as all recoverable data has already been
read.
> Entry missing from ZIP
> ----------------------
>
> Key: COMPRESS-420
> URL: https://issues.apache.org/jira/browse/COMPRESS-420
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers
> Affects Versions: 1.13, 1.14
> Reporter: Luke Quinane
> Attachments: missing-entry.zip, test.zip
>
>
> There seems to be some regression introduced in v1.13 which means that the
> second entry in the attached ZIP is no longer exposed via:
> '{{zipFile.getEntries();}}'.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
