[ https://issues.apache.org/jira/browse/AVRO-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119585#comment-17119585 ]
ASF subversion and git services commented on AVRO-2649: ------------------------------------------------------- Commit 1c5e32d2b98e193ea048f8ece8ee3984c6165bfe in avro's branch refs/heads/master from Daniel Kulp [ https://gitbox.apache.org/repos/asf?p=avro.git;h=1c5e32d ] [AVRO-2649] Better fix for allowing args in various orders > [Java] Argument order enforced in avro-tools cli. > ------------------------------------------------- > > Key: AVRO-2649 > URL: https://issues.apache.org/jira/browse/AVRO-2649 > Project: Apache Avro > Issue Type: Improvement > Affects Versions: 1.9.1 > Reporter: Ryan Skraba > Priority: Minor > Fix For: 1.10.0 > > > The following command line works: > {code} > $ avrotool compile -string -bigDecimal schema > ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output > Input files to compile: > ./lang/java/tools/src/test/compiler/input/fieldtest.avsc > {code} > Switching the first two flags causes an error: > {code} > $ avrotool compile -bigDecimal -string schema > ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output > Expected "schema" or "protocol". > {code} > There's really no need to enforce a command line option order, especially for > flags, and it's not user friendly. Most CLI tools don't. There's several > good command line parsers to help. -- This message was sent by Atlassian Jira (v8.3.4#803005)