[
https://issues.apache.org/jira/browse/COMPRESS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141008#comment-14141008
]
Stefan Bodewig commented on COMPRESS-289:
-----------------------------------------
Just realized the same problem also shows up for the PAX header entry and while
I fixed this a test wen't into a inifinite recursion because the last modified
time for the PAX header would trigger yet another PAX header ...
See svn revision 1626290
> 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)
