commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [compress] (Internal)LZWInputStream
Date Sun, 01 Feb 2015 16:40:50 GMT
All I care about is binary compatibility in a minor release for most cases
(not 80% of the cases, but more like 99.9%). I do not want to be in jar


On Sun, Feb 1, 2015 at 1:04 AM, Stefan Bodewig <> wrote:

> Hi
> I'm trying to bring together two separate discussions from two different
> [VOTE]-threads.  It seems as if I should cancel the RC2 vote and before
> I rush another RC maybe we can get consensus on what to do.
> * my experiments show that moving the LZWInputStream class hasn't got as
>   big an impact on subclasses of ZCompressorInputStream as I and others
>   would have expected.  This likely means we can relax the warning of
>   the release notes and site again.  Right?  Is anybody going to perform
>   more experiments?
> * (Internal)LZWInputStream has a bunch of protected fields that slipped
>   through a few releases ago.  We should add getter/setter pairs and
>   deprecate using the fields.  Sebb would like to even make the fields
>   private assuming the chance of people actually subclassing
>   ZCompressorInputStream and using said fields is very small.
> Any opinions?
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message