The raw .json file is available from this link: https://raw.githubusercontent.com/timtiemens/javacommandlineparser/master/java-parsers.json
Below is a table showing Java command-line parsing libraries, sorted by name. "Rank" is my rank for the library (1 to 4, or blank). "Annotation" indicates the library uses Java annotations for argument metadata (i.e. "good"). "KeyValue" indicates that the library uses Java map structures to store and access the arguments (i.e. "bad").
| Name | Rank | Lang | Annotation | KeyValue | Notes |
|---|---|---|---|---|---|
| Airline | java | X | |||
| argot | scala | abandoned - see scopt | |||
| argparse4j | java | ||||
| argparser | java | X | create individual options, where options are "holders", parse() into the holders | ||
| args4j | 3 | java | X | field-based, unclear if "--long-Name" is supported | |
| clajr | java | ||||
| cli-parser | java | ||||
| CmdLn | java | X | |||
| Commandline | java | X | |||
| DocOpt.java | java | X | weird String-based approach to defining argument names and help at the same time. port of docopt. | ||
| dolphin getopt | java | ||||
| DPML CLI | java | Jakarta Commons CLI2 fork | |||
| Dr. Matthias Laux | java | ||||
| Jakarta Commons CLI | java | X | like JArgs, except key is "String", not an Option object | ||
| jargo | java | X | |||
| jargp | java | ||||
| JArgs | java | X | single "parse" call with array of options, key is an Option object | ||
| java-getopt | java | ||||
| jbock | java | X | |||
| JCLAP | java | ||||
| jcmdline | java | ||||
| JCommander | 1 | java | X | good documentation, custom parser, validation | |
| JCommando | java | generates .java, but still requires an additional .jar | |||
| JewelCLI | 4 | java | X | interface-based but can be instance-based with setters | |
| JOpt simple | java | X | |||
| JSAP | java | X | old (2008) not well documented | ||
| naturalcli | java | ||||
| Object Mentor CLI article dead link | java | ||||
| optional | scala | multiple github forks | |||
| parse-cmd | java | ||||
| picocli | 2 | java | X | good documentation - documentation looks suspiciously like it is patterned after JCommander | |
| ritopt | java | ||||
| Rop | java | ||||
| scopt | scala | ||||
| TE-Code Command | java |
- API uses annotations, not key-value
- Generates help
- Short (-v) and Long (--verbose) parsing to same field
- Sub-commands (git add ...), can have their own options
- License (i.e. not GPL)
- Does not depend on other libraries
- Java version
- Java Command-Line Interfaces (Part N of 30) number 1 covers Commons-CLI, number 2 covers args4j, number 7 covers JCommander, number 21 covers Airline, number 28 covers getopt4j, and number 30 is a summation and "5 most likely to succeed" (commons-CLI, args4j, JCommander, JewelCLI, picocli) section. http://marxsoftware.blogspot.com/ - See 2017 June to November
- Maven Repository Command Line Parsers category 2018 September sorted by popularity: commons-CLI, JCommander, args4j, jopt-simple, scopt, argparse4j, Airline, JSAP. https://mvnrepository.com/open-source/command-line-parsers
- stackoverflow 2008 December https://stackoverflow.com/questions/367706/how-do-i-parse-command-line-arguments-in-java
- stackoverflow 2009 October (marked duplicate) https://stackoverflow.com/questions/1524661/the-best-cli-parser-for-java
- stackoverflow 2011 September https://stackoverflow.com/questions/7341683/parsing-arguments-to-a-java-command-line-program/7341992
- JewelCli alternatives list http://jewelcli.lexicalscope.com/related.html
- Compare JCommander and picoli https://java.libhunt.com/compare-picocli-vs-jcommander?rel=cmp-lib
- Picoli alternatives list and feature charts https://github.com/remkop/picocli/wiki/CLI-Comparison