You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/05/05 04:16:00 UTC
[jira] [Closed] (JAMES-1649) James CLI should be easier to use.
[ https://issues.apache.org/jira/browse/JAMES-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-1649.
---------------------------------
Resolution: Won't Fix
> James CLI should be easier to use.
> ----------------------------------
>
> Key: JAMES-1649
> URL: https://issues.apache.org/jira/browse/JAMES-1649
> Project: James Server
> Issue Type: Improvement
> Components: CLI
> Affects Versions: Trunk
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: Trunk
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Why ?
> - It is nearly impossible to read James CLI help message
> - James CLI command line naming is obscure, too long and too monolitic
> - No precise help.
> - No auto completion / partial non ambiguous command interpretation
> How ?
> - Create a top level group entity for commands. This way we keep automatic and adaptative help generation.
> - As they are space separated, command names will get easier to read
> - Attach description for thes functionnality group.
> Example syntax :
> james-cli.sh FUNCTIONNALITY \[EXTRA SPECS...\] COMMAND \[ARGS... \]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org