On 2015-02-02, Damjan Jovanovic wrote:
I have a patch waiting to be committed to commons-imaging which uses
the LZW stuff in commons-compress (brief mention of it by me on
IMAGING-126), so it could break with these changes. My hope was to
wait for the next release of compress before
Send from my mobile device
Am 01.02.2015 um 07:04 schrieb Stefan Bodewig bode...@apache.org:
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 Sun, Feb 1, 2015 at 7:04 AM, Stefan Bodewig bode...@apache.org wrote:
* (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
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
hell.
Gary
On Sun, Feb 1, 2015 at 1:04 AM, Stefan Bodewig bode...@apache.org wrote:
Hi
I'm trying to bring together two separate discussions from
On 1 February 2015 at 18:33, Jochen Wiedmann jochen.wiedm...@gmail.com wrote:
On Sun, Feb 1, 2015 at 7:04 AM, Stefan Bodewig bode...@apache.org wrote:
* (Internal)LZWInputStream has a bunch of protected fields that slipped
through a few releases ago. We should add getter/setter pairs and
Hi
I have a patch waiting to be committed to commons-imaging which uses
the LZW stuff in commons-compress (brief mention of it by me on
IMAGING-126), so it could break with these changes. My hope was to
wait for the next release of compress before committing, so I could
use that version of
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
