On 2009-02-10, Stefan Bodewig wrote:
> On 2009-02-10, Torsten Curdt wrote:
>> No particular objections. Not sure it helps much though :)
> True.
Actually it hurts.
Via FilterOutputStream a call to ArchiveOutputStream.flush() would
suddenly flush the wrapped stream where it had been a no-op f
On 2009-02-10, Torsten Curdt wrote:
> No particular objections. Not sure it helps much though :)
True.
I'll probably try to find out why ZipArchiveOutputStream extended
FilterOutputStream in the first place - probably because
java.util.zip.ZipOutputStream does and Ant's class should be as close
No particular objections. Not sure it helps much though :)
cheers
--
Torsten
On Sat, Feb 7, 2009 at 15:14, Stefan Bodewig wrote:
> Hi,
>
> I change ArchiveOutputStream extend FilterOutputStream while I
> modified ZipArchiveOutputStream and it seems a very natural thing to
> do for all the other
Hi,
I change ArchiveOutputStream extend FilterOutputStream while I
modified ZipArchiveOutputStream and it seems a very natural thing to
do for all the other streams as well.
All concrete compressor/archiver streams have constructors that take a
different stream as their argument and most of them
