You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "A. Soroka (JIRA)" <ji...@apache.org> on 2015/06/11 20:32:00 UTC

[jira] [Commented] (JENA-960) The construction of jena-cmd

    [ https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582341#comment-14582341 ] 

A. Soroka commented on JENA-960:
--------------------------------

I understood your comment on the email list to be describing a module that would centralize and host the command-framework and commands for modules on which it depends, but perhaps you are talking about just the command-framework, with modules themselves hosting the commands related to their functionality? 

> 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)