[
https://issues.apache.org/jira/browse/KAFKA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128973#comment-16128973
]
Paolo Patierno commented on KAFKA-5723:
---------------------------------------
[~adyachkov] sure you can. I think that for having more people working on
different tools but with a common way (i.e. some common classes for options and
so on) we should be able to commit these common classes first so that people
can use them. For now it's all on my fork. Having these common classes
committed to the Kafka project could help the development, at least in a branch
not on trunk. I don't know if something like this already happened in the past
and what the approach was. Maybe [~ijuma] can give us some advices on that ?
> Refactor BrokerApiVersionsCommand to use the new AdminClient
> ------------------------------------------------------------
>
> Key: KAFKA-5723
> URL: https://issues.apache.org/jira/browse/KAFKA-5723
> Project: Kafka
> Issue Type: Improvement
> Reporter: Viktor Somogyi
> Assignee: Viktor Somogyi
>
> Currently it uses the deprecated AdminClient and in order to remove usages of
> that client, this class needs to be refactored.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
