edin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
From: Paolo Patierno
Sent: Monday, July 10, 2017 11:44 AM
To: dev@kafka.apache.org
Subject: Re: From Scala to Java based tools :
lopatierno.wordpress.com/>
From: Paolo Patierno
Sent: Monday, July 10, 2017 8:31 AM
To: dev@kafka.apache.org
Subject: Re: From Scala to Java based tools : joptsimple vs argparse4j
Hi Tom,
no I have no specific reason but I'd like to know why it was chosen for the
S
: DevExperience<http://paolopatierno.wordpress.com/>
From: Tom Bentley
Sent: Monday, July 10, 2017 8:29 AM
To: dev@kafka.apache.org
Subject: Re: From Scala to Java based tools : joptsimple vs argparse4j
Hi Paolo,
I don't have an opinion about which you should
Hi Paolo,
I don't have an opinion about which you should use, but I certainly agree
that two option parsing dependencies appears to be 1 too many.
Is there a reason why you prefer joptsimple?
Cheers,
Tom
On 10 July 2017 at 08:38, Paolo Patierno wrote:
> Hi devs,
>
>
> working on re-writing t
Hi devs,
working on re-writing the TopicCommand tool in Java using the Admin Client, I
was asking if there is any specific reason why the Scala tools use joptsimple
for parsing command line arguments while the current Java based tools use
argparse4j.
I'd like to use the joptsimple even for th
