[ https://issues.apache.org/jira/browse/COMPRESS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305587#comment-16305587 ]
Stefan Bodewig commented on COMPRESS-420: ----------------------------------------- It looks as if I was wrong and it is not COMPRESS-267 alone. If I change the code to return {{null}} rather than throw the exception introduced with https://issues.apache.org/jira/secure/attachment/12835792/0001-COMPRESS-367-Throw-ZipException-on-invalid-entry-wit.patch you still only get two entries. So the result is the same as catching the exception. I need to find out why you've been able to get further than the second entry in 1.12, time for some bisecting. > 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 > Fix For: 1.16 > > 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)