[
https://issues.apache.org/jira/browse/ANY23-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney closed ANY23-71.
-------------------------------------
Bulk close for 0.7.0-incubating release
> improve the current CLI engine
> ------------------------------
>
> Key: ANY23-71
> URL: https://issues.apache.org/jira/browse/ANY23-71
> Project: Apache Any23
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.7.0
> Reporter: Simone Tripodi
> Assignee: Michele Mostarda
> Fix For: 0.7.0
>
> Attachments: enhanced_cli.patch
>
>
> Actual CLI - even if nicely working - can be improved in therms of of both
> internal architecture and user interface.
> I see two main "issues" on current CLI:
> * on UI, the CLI exposes internal details, since the {{ToolRunner}} requires
> the classname of the tool has to be executed;
> * on internals, each Tool has to parse the the chunk of the command line,
> which can be automated.
> So my proposal is to automate, via the already working plugins discovery, the
> CLI arguments parsing AND implementing a svn/git commands-based alike
> interface.
> My preferred choice for that is [JCommande|http://www.jcommander.org/]
> because:
> * it allows binding CLI arguments to Java properties via Annotations - no
> more manual parsing;
> * it already supports a complex syntax to implement
> [commands|http://jcommander.org/#Complex];
> * commands aliases can be expressed via annotations - no more needs to
> expose internals;
> Patch with proposal is coming
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
