Corrupt input data when using LZFInputStream and jets3t about compress HOT 6 CLOSED

Thanks. I'll see how we can improve this.

from compress.

Ok; I think I have fixed one thing that could have triggered this -- header reading was naively assuming that read for 5 bytes is guaranteed to read 5 bytes (should have fixed that earlier when I resolved other similar issues).
Can you see if this takes care of the problem? (in trunk, will be in 0.8.0)

from compress.

Hi, I'll try to test this change tomorrow or Wednesday.

from compress.

Hopefully this will fix the issue (it definitely sounds like issue I fixed could cause problems like you describe) -- 0.8.0 is now out anyway, let me know either way.

from compress.

I've tested this and it seems to fix it. Thanks!

I haven't been able to test it on the same machine where I initially saw the issue yet, but I don't expect that to make a difference, so I'll close the issue now. I can always reopen if I see it again.

By the way, 0.8.0 in Maven doesn't include the source jar for some reason (unlike previous releases).

from compress.

Ok thanks for checking it out.

Lack of sources is probably related to a warning I saw -- for some reason Maven was complaining about classifier... not sure what/why/how caused that; maybe my use of Maven 3 (due to upgrade MacOS decided was necessary).

from compress.