[
https://issues.apache.org/jira/browse/KAFKA-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240067#comment-16240067
]
Tom Bentley commented on KAFKA-6174:
------------------------------------
[~ijuma] binary compatibility checking could be something done in CI, since
there are tools (e.g. https://lvc.github.io/japi-compliance-checker/,
http://siom79.github.io/japicmp/) which can detect this sort of thing.
> Add methods in Options classes to keep binary compatibility between 0.11 and
> 1.0
> --------------------------------------------------------------------------------
>
> Key: KAFKA-6174
> URL: https://issues.apache.org/jira/browse/KAFKA-6174
> Project: Kafka
> Issue Type: Bug
> Reporter: Dong Lin
> Assignee: Dong Lin
> Fix For: 1.0.1
>
>
> From 0.11 to 1.0, we moved `DescribeClusterOptions timeoutMs(Integer
> timeoutMs)` from DescribeClusterOptions to AbstractOptions. User reports that
> code compiled against 0.11.0 fails when it is executed with 1.0 kafka-clients
> jar.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
