commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject [compress] nearing 1.13 release, backwards incompatible change(?)
Date Thu, 22 Dec 2016 07:28:11 GMT
Hi

I've managed to build japicmp reports for COMPRESS, the full site of the
current master is at
http://stefan.samaflost.de/staging/commons-compress-1.13/

If you look at
http://stefan.samaflost.de/staging/commons-compress-1.13/japicmp-maven-plugin-report.html
you'll see a few strange things. Some new methods and classes are
flagged as binary incompatible because they throw checked
exceptions. This seems to be japicmp, not a real issue with the code.

But there is one binary incompatible change (a serialization
incompatibility): UnsupportedZipFeatureException has a new
serialVersionUID. This is because it really changed its serialization
from not being serializable at all to being serializable (the old code
had non-transient non-serializable fields).

I think this is acceptable.

Could you please look over the reports and at the current code base to
determine whether there is anything that needs to get fixed before
cutting a release?

Thanks

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message