commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMPRESS-390) Expose zip stream offset and size via API
Date Wed, 26 Apr 2017 04:55:04 GMT

    [ https://issues.apache.org/jira/browse/COMPRESS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984169#comment-15984169
] 

ASF GitHub Bot commented on COMPRESS-390:
-----------------------------------------

Github user coveralls commented on the issue:

    https://github.com/apache/commons-compress/pull/22
  
    
    [![Coverage Status](https://coveralls.io/builds/11244036/badge)](https://coveralls.io/builds/11244036)
    
    Coverage decreased (-0.02%) to 84.286% when pulling **2d3da5a265a42046c15311ecd23554c28c158e95
on kvr000:feature/COMPRESS-390-expose-file-offset-via-api** into **0ee8f1e8ab53746ea9f735aa07e857a0c4e55656
on apache:master**.



> Expose zip stream offset and size via API
> -----------------------------------------
>
>                 Key: COMPRESS-390
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-390
>             Project: Commons Compress
>          Issue Type: New Feature
>          Components: Archivers
>    Affects Versions: 1.13
>            Reporter: Zbynek Vyskovsky
>              Labels: features
>             Fix For: 1.14
>
>
> In certain cases it may be useful to get information about where in the archive the stream
starts and ends. Typically when zip is used as resource container and the resources are then
mapped directly into memory, but not only.
> The size and compressed size are already available but not the stream offset.
> This can be applied to other archive types as well, therefore it would make sense to
put this into basic interface - ArchiveEntry. But not necessarily all of them have to support
it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message