You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/06/10 12:06:00 UTC
[jira] [Commented] (JENA-960) The construction of jena-cli
[ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580338#comment-14580338 ]
Andy Seaborne commented on JENA-960:
------------------------------------
Dependency the other way round? DSB.TDB depend on jena-cmd
I tend to favour "jena-cmd" to "jena-cli" because it's not just the command line processing but a command framework; also a little less confusion with Common CLI.
> The construction of jena-cli
> ----------------------------
>
> 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-cli}}. 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)