commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMPRESS-289) TarArchiveOutputStream includes timestamp in long link headers
Date Fri, 19 Sep 2014 17:50:33 GMT

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

Stefan Bodewig commented on COMPRESS-289:
-----------------------------------------

Thanks Bob

I've taken a slightly different approach using the last modification time of the entry the
long name entry belongs to.  Your unit test (moved to a different test class) still passes.
 Please see svn revisions 1626280 and 1626284.

> TarArchiveOutputStream includes timestamp in long link headers
> --------------------------------------------------------------
>
>                 Key: COMPRESS-289
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-289
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Archivers
>    Affects Versions: 1.8.1
>            Reporter: Bob Robertson
>            Priority: Trivial
>              Labels: patch
>             Fix For: 1.9
>
>         Attachments: TarArchiveOutputStream.java.patch, TarTestCase.java.patch
>
>
> When I create a Tar Archive Entry with a long name, the Long Link Entry contains a default
modification date of the current Date.
> This results in two archives with the same contents having different MD5 checksums.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message