Jane,
I agree, but what Bill suggested is something that
we have been wanting to do for some time. We need to do something
to separate the options for the commands from the options for the
asadmin program. Currently, a command implementation does not care
what the values for:
-- host, --port, --passwordfile, --secure, --terse etc. are.
All of these are "asadmin program options". A command like create-http-listener
does not care about it.
A via-media solution can be reached (more specification required), if we
say that a command name can't start with a - or a --. This is intuitive
and can take care of our requirement.
Again, think of what we want to do with this proposal. I think it is useful.
Regards,
Kedar
PS- BTW, I am not so sure that --target is an asadmin program option. A command
does care about what the value of --target is. So, the current discussion is
rather unrelated with documentation of --target option.
Jane Young wrote:
> Hi Kedar et al,
>
>
> >In v3, can I say "asadmin --target foo list"? That is, can all the
> >common arguments that really apply to asadmin itself rather than the
> >subcommands be specified *before* the subcommand?
>
> This is *not* CLIP compliant. Please see:
> http://www.opensolaris.org/os/community/arc/caselog/1999/645/spec-html/
> Also, there is ambiguity if options are specified *before* the subcommand.
> Consider the example:
>
> "asadmin --option-name foo bar" What if --option-name is a boolean
> option. So is foo treated as an option value to option-name or is it
> treated as a subcommand? Note that boolean option does not require a
> option value.
> Jane
>
>
> Prashanth Abbagani wrote:
>
>>
>>
>> Kedar Mhaswade wrote:
>>
>>>
>>>
>>> Bill Shannon wrote:
>>>
>>>> Kedar Mhaswade wrote:
>>>>
>>>>> Folks,
>>>>>
>>>>> *For Prelude*, I feel that all the man-pages should do a better job of
>>>>> "hiding" the --target from readers mainly because we are not utilizing
>>>>> the targets for Prelude. Providing information regarding targets
>>>>> generally confuses the intended users of Prelude, IMO.
>>>>>
>>>>> Can all the commands just not mention any information for target for
>>>>> Prelude? We will reinstate --target for v3 final.
>>>>
>>>>
>>>> In v3, can I say "asadmin --target foo list"? That is, can all the
>>>> common arguments that really apply to asadmin itself rather than the
>>>> subcommands be specified *before* the subcommand? If so, why don't
>>>> we document it that way, even though the options can also be specified
>>>> after the subcommand?
>>>
>>>
>>> Yes, for v3 final.
>>> No, for Prelude.
>>>
>>> Yes, it will be handled in a backward incompatible manner.
>>
>> I liked the Idea. But before committing on that, we need to check if
>> its CLIP compliant. I think its not, someone has to verify it.
>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>