[
https://issues.apache.org/jira/browse/AVRO-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117011#comment-17117011
]
Hudson commented on AVRO-2649:
------------------------------
FAILURE: Integrated in Jenkins build AvroJava #892 (See
[https://builds.apache.org/job/AvroJava/892/])
AVRO-2649 Made argument order non-enforceable avro-tools cli (#741) (github:
[https://github.com/apache/avro/commit/7fd098a56064ece218c66ba1d2ad78bd358f6009])
* (edit)
lang/java/tools/src/main/java/org/apache/avro/tool/SpecificCompilerTool.java
* (edit)
lang/java/tools/src/test/java/org/apache/avro/tool/TestSpecificCompilerTool.java
> [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)
