[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588088#comment-14588088
]
Rob Vesse commented on JENA-960:
--------------------------------
Well speaking for Airline which I've spent a lot of time on and which I've used
for a number of both open source and proprietary projects in terms of parsing
it seems to provide most of the capabilities Jena would need:
* Ability to define options which take configurable numbers of parameters
* Ability to encapsulate related options into reusable classes
* Ability to define both long and short form options
* Ability to provide detailed built-in help
In terms of execution Airline leaves that up to the end user, there are some
standard patterns I tend to use but ultimately that is up to the implementor
Take a look at the
[examples|https://github.com/rvesse/airline/tree/master/examples/src/main/java/com/github/rvesse/airline/examples]
and see if those look like they do the kinds of things Jena needs.
For a more concrete example see
[RdfStats|https://github.com/apache/jena/blob/master/jena-elephas/jena-elephas-stats/src/main/java/org/apache/jena/hadoop/rdf/stats/RdfStats.java]
in the Elephas packages.
> The construction of jena-cmd
> ----------------------------
>
> Key: JENA-960
> URL: https://issues.apache.org/jira/browse/JENA-960
> Project: Apache Jena
> Issue Type: Epic
> Components: Jena
> Reporter: A. Soroka
> Priority: Minor
> Labels: cli, command-line, commandline
>
> The current machinery supporting Jena's CLI tools is too sophisticated to be
> replaced entirely by off-the-shelf parts, but it is also scattered across
> several modules. That's not necessary and it could be improved by
> constructing a centralizing module {{jena-cmd}}. This module would depend on
> SDB, TDB, and any other module that exports CLI tools as products.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
