seemingly duplicate functionality between TarArchive*putStream and
Tar*putStream classes
----------------------------------------------------------------------------------------
Key: SANDBOX-281
URL: https://issues.apache.org/jira/browse/SANDBOX-281
Project: Commons Sandbox
Issue Type: Improvement
Components: Compress
Affects Versions: Nightly Builds
Environment: I use win xp sp3, but this is probably irrelevant
Reporter: Sam Smith
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
