Paul Davies wrote:
> Hi,
>> *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 fact, this issue needs to be addressed for all unsupported options in
> prelude, not just --target.
>
> Is a definitive, comprehensive list of the options that each command
> will support at v3 Prelude available anywhere? To be able to make the
> required changes by HCF, I need this information *urgently*.
All remote commands have exact same set of common options. This has
not changed from GlassFish V2 with the only exception of --secure (which
needs to be determined, see issue: 5570
https://glassfish.dev.java.net/issues/show_bug.cgi?id=5570
I was thinking specifically in terms of --target as that specifies
a remote server instance or a cluster which might be accessed depending
upon the value. Since the only target available for Prelude is the
only server (call it DAS or whatever), I thought we can safely remove
that for now rather than accept a value for it and then ignore it.
If it's too much of work, let's not to do it. It was just a thought.
-Kedar
>
> Thanks!
> --
> Paul Davies, Senior Technical Writer, Sun Microsystems, Inc.
> http://blogs.sun.com/techscribe/