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

Andy Seaborne edited comment on JENA-960 at 6/25/15 8:46 AM:
-------------------------------------------------------------

> Why have Jena-specific code to parse flags etc

That is not the question - it exists and has for a long time. (When it was 
written, there were no suitable libraries I could find and I looked 
repeatedly.) 

These change proposals are all too vague. Change for changes sake is not free. 
I see no proposal here that suggests it is better for end users. What we have 
so far is suggestions of change that will mostly break someone's scripts.

I would like to see a concrete proposal with identified differences : are flags 
and values handled in the same way? Is compatibility a goal? Is there something 
wrong with the current command line handling? Who and what will be affected by 
change?







was (Author: andy.seaborne):
> Why have Jena-specific code to parse flags etc

That is not the question - it exists and has for a long time. (When it was 
written, there were no suitable libraries I could find and I looked 
repeatedly.) 

These change proposals are all too vague. Change of changes sake is not free. I 
see no proposal here that suggests it is better for end users. What we have so 
far is suggestions of change that will mostly break someone's scripts.

I would like to see a concrete proposal with identified differences : are flags 
and values handled in the same way? Is compatibility a goal? Is there something 
wrong with the current command line handling? Who and what will be affected by 
change?






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

Reply via email to