Bill Shannon 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.
>
> Does that mean for Prelude I would have to say "asadmin list --target
> server"?
> Or does that mean for Prelude "--target" isn't even allowed?
>
The default value of --target is null which means the only server
available in Prelude.
As of now, --target is allowed, but serves no useful purpose for Prelude
and that's why I raised this.
>> Yes, it will be handled in a backward incompatible manner.
>
> Um, that doesn't sound good.
Oops, I meant ... in compatible manner. Argh.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>