[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680120#comment-14680120
]
A. Soroka commented on JENA-960:
--------------------------------
In fact, the command line processing code remains scattered across
{{jena-base}} and {{jena-arq}}. For example, command-line-related classes in
{{jena-tdb}} inherit from command line-related classes in {{jena-arq}}. I was
unable to centralize it in {{jena-base}} because much of the code is
undocumented and I do not understand what the workflow or dependencies are. I
would be happy to open a new ticket to document them.
> 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
> Fix For: Jena 3.0.0
>
>
> 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)
