You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2010/03/09 18:21:27 UTC

[jira] Updated: (COMPRESS-18) JarArchiveEntry does not populate manifestAttributes or certificates

     [ https://issues.apache.org/jira/browse/COMPRESS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated COMPRESS-18:
-----------------------------------

    Attachment: compress-18.patch

a re-implementation of the jar package using java.util.jar rather than our own zip package.

This has some backwards compatibility issues:

* Jar*Stream and JarArchiveEntry now have different base classes than before
* the stream constructors throw exceptions and I had to wrap the IOException or would have been forced to allow the factory methods to to throw IOException which would have been even worse looking at it WRT backwards compatibility
* you can't have an empty jar file - java.util.zip.ZipOutputStream throws an exception
* I've removed the getManifestAttributes method that never worked anyway, this could be fixed
* you can't add a ZipArchiveEntry to a JarInputStream, this could be fixed if we wanted to

the patch itself doesn't address the count() methods in Archive*Stream, this can easily be added by using something like the CountingStream I added to CpioArchiveOutputStream in svn revision 911031 and removed again later

> JarArchiveEntry does not populate manifestAttributes or certificates
> --------------------------------------------------------------------
>
>                 Key: COMPRESS-18
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-18
>             Project: Commons Compress
>          Issue Type: Bug
>            Reporter: Sebb
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: compress-18.patch
>
>
> JarArchiveEntry does not populate manifestAttributes or certificates - they are both always null.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.