Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E8C07200CC1 for ; Mon, 10 Jul 2017 19:31:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E7339163C50; Mon, 10 Jul 2017 17:31:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 38A76163C4D for ; Mon, 10 Jul 2017 19:31:05 +0200 (CEST) Received: (qmail 55144 invoked by uid 500); 10 Jul 2017 17:31:04 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 55132 invoked by uid 99); 10 Jul 2017 17:31:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2017 17:31:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F241B193DE0 for ; Mon, 10 Jul 2017 17:31:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id IH0BsX8R8jwR for ; Mon, 10 Jul 2017 17:31:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E5FC56268F for ; Mon, 10 Jul 2017 17:31:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6537AE0ADD for ; Mon, 10 Jul 2017 17:31:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 36B81246A9 for ; Mon, 10 Jul 2017 17:31:00 +0000 (UTC) Date: Mon, 10 Jul 2017 17:31:00 +0000 (UTC) From: "Paolo Patierno (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-5536) Tools splitted between Java and Scala implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Jul 2017 17:31:06 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080704#comment-16080704 ] Paolo Patierno commented on KAFKA-5536: --------------------------------------- Thanks Ismael ! 1. Good. I can recover the previous work I have done using argparse4j. In any case my idea is to mimic the same behaviour we have with the joptsimple lib in order to avoid problems. 2. Regarding sharing the code, the CommandLineUtils leverages on the joptsimple lib so it's not possible just move it to use argparse4j in Java and then sharing with other Scala tools (even because the migration will be slow, tool by tool and not all together). So it seems that the better solution for now is just rewriting for the tools module. Let's see how things will evolve on TopicCommand, the first tool that will be the subject of this big migration. > Tools splitted between Java and Scala implementation > ---------------------------------------------------- > > Key: KAFKA-5536 > URL: https://issues.apache.org/jira/browse/KAFKA-5536 > Project: Kafka > Issue Type: Wish > Reporter: Paolo Patierno > > Hi, > is there any specific reason why tools are splitted between Java and Scala implementations ? > Maybe it could be better having only one language for all of them. > What do you think ? > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.14#64029)