commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Binary compatibility report
Date Sun, 05 Jun 2016 08:31:02 GMT
On 4 June 2016 at 15:19, Ponomarenko Andrey <andrewponomarenko@yandex.ru> wrote:
> Hello,
>
> I've just prepared the report on backward compatibility for the Commons IO library (BC
— binary compatibility, SC — source compatibility): http://abi-laboratory.pro/java/tracker/timeline/commons-io/

Thanks for the links.

However I found it difficult to understand the output.
For example, why are some backgrounds green and some yellow?

Also, what are the rules that are used to determine whether or not a
change affects compatibility?
How do these compare with Clirr?

I think there's a bug:

The low level warning here

http://abi-laboratory.pro/java/tracker/compat_report/commons-io/1.4/2.0/8be39/bin_compat_report.html#Type_Problems_Low

says that it was caused by the change:

"Added super-class java.lang.Object."

That's not possible as a change.

> The report is generated daily by the japi-compliance-checker and japi-tracker tools:
>
> https://github.com/lvc/japi-compliance-checker (generates individual reports for particular
versions of the library)
> https://github.com/lvc/japi-tracker (generates the timeline report)
>
> I can add more libraries to the tracker if somebody is interested (just reply this Email
with the list of library names to add). Current list of maintained libraries: http://abi-laboratory.pro/java/tracker/
>
> Thank you.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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


Mime
View raw message