[jboss-as7-dev] CLI arguments convention

[Alexey Loubyansky]

On 04/19/2011 04:29 PM, David M. Lloyd wrote:
> On 04/19/2011 08:31 AM, Alexey Loubyansky wrote:
>>
>> In addition, it's kind of a proprietary convention. We discussed this
>> with Max today and I'm looking into the GNU convention for command line
>> arguments
>
> That is a common convention -- for command line arguments.  For
> interactive command lines (examples I'm thinking of include 3com and
> Cisco network management CLIs, as well as commands such as linux's "ip"
> command which have widely variable arguments), usually it's more like:
>
> create-jms-cf name mycf entries foo bar baz

Here is the full version

[localhost:9999 /] create-jms-cf

--help                            name= 
auto-group=
entries=                          connector= 
block-on-acknowledge=
block-on-durable-send=            block-on-non-durable-send= 
cache-large-message-client=
call-timeout=                     client-failure-check-period= 
client-id=
confirmation-window-size=         connection-ttl= 
consumer-max-rate=
consumer-window-size=             discovery-group-name= 
dups-ok-batch-size=
failover-on-initial-connection=   failover-on-server-shutdown= 
group-id=
max-retry-interval=               min-large-message-size= 
pre-acknowledge=
producer-max-rate=                producer-window-size= 
reconnect-attempts=
retry-interval=                   retry-interval-multiplier= 
scheduled-thread-pool-max-size=
thread-pool-max-size=             transaction-batch-size= 
use-global-pools=


> Of course this falls apart for "deploy" unless you do something like this:
>
> deploy file mything.war as myblah.war runtime-name yourblah.war
>
> or something (i.e. make it somewhat more fluent and less shell-ish).

Ok, so you'd actually prefer a simplicity instead of a standard convention.
I'll think about it (and if somebody has suggestions, please, share) but 
if that doesn't work out we'll have to choose an existing convention.

>> And another point is the use of '='. Some command lines don't use it, e.g.
>>
>> deploy --file my.war --name my_war_name.war --runtime-name
>> my_war_runtime_name.war
>>
>> and some do
>>
>> deploy --file=my.war --name=my_war_name.war
>> --runtime-name=my_war_runtime_name.war
>
> And some command lines support both :)

That's too messy, IMO.

Thanks,
Alexey