[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599522#comment-14599522
]
A. Soroka commented on JENA-960:
--------------------------------
Did we come to some conclusion about the direction of dependency here? It seems
that [~andy.seaborne] was thinking of a low-level module that would provide the
machinery out of which to construct commands and execute them, and then other
modules that want to publish functions to the CLI would use that machinery.
That sounds good to me. Is that the plan?
As far as libraries go, my thought was to use good off-the-shelf parts for as
much as we can. Why have Jena-specific code to parse flags etc. when there
exists perfectly good reusable code for those purposes (e.g. Airline, which is
already part of the project via Elephas)?
> 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)
