[COMPRESS-49] seemingly duplicate functionality between TarArchive*putStream and Tar*putStream classes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0

Environment

I use win xp sp3, but this is probably irrelevant

• Assignee: Unassigned
• Reporter: Sam Smith
• Created: 10/Feb/09 16:29
• Updated: 24/Mar/09 05:09
• Resolved: 10/Feb/09 16:35

Description

When I first looked at the Compress API, I began using the TarInputStream/TarOutputStream classes. But now I notice that there is also the TarArchiveInputStream/TarArchiveOutputStream classes. They seems fairly related to me, with a lot of duplicate functionality.

In private email conversation with the developer Torsten Curdt about this, he wrote:

**********
You should be using TarArchive*putStream. All options should be available on the TarArchiveEntry. Which makes me wonder whether we should make the Tar*putStream classes package/private ...or merge them.
**********

I agree that the Tar*putStream classes should be merged or hidden in order to eliminate developer confusion, but ONLY AFTER you have the Tar*putStream classes truly support all options.

Here is a critical one for me: I need long path name support, and said option is available on TarOutputStream via its setLongFileMode(int longFileMode) method, but I do not see that anywhere in TarArchiveOutputStream. There may be some more options like this.