dev@glassfish.java.net

Re: javadocs for glassfish and related modules.

From: Rajiv Mordani <rajiv.mordani_at_sun.com>
Date: Tue, 24 Nov 2009 17:12:13 -0800

Hi Tim,
    Do you know how you can specify in javadoc to exclude one class? I
can add the rest.

- Rajiv

Tim Quinn wrote:
> Rajiv,
>
> Are you willing to accept more requests to publish parts of the
> JavaDoc? :-)
>
> If so, can you please add
>
> org.glassfishappclient.client.acc.AppClientContainer (ideally just the
> one class from that package) from the appclient/client/acc module
>
>
> org.glassfish.appclient.client.acc.config (ideally omitting the
> AdapterN.java classes) from the appclient/client/acc-config module
>
>
> to the list?
>
> Many thanks.
>
> - Tim
>
> Eduardo Pelegri-Llopart wrote:
>> Very cool.
>>
>>
>> Alexis Moussine-Pouchkine wrote:
>>>
>>> On Nov 24, 2009, at 7:26, Rajiv Mordani wrote:
>>>
>>>> I have a first stab at the javadocs and they are published at
>>>>
>>>> http://javadoc.glassfish.org/v3/apidoc/
>>>>
>>>> Alexis I will include the packages you list below.
>>>
>>> Excellent, thanks.
>>> -Alexis
>>>
>>>> I am debugging an issue about ClassCastException while generating
>>>> javadocs for certain packages.
>>>>
>>>> - Rajiv
>>>>
>>>> Alexis Moussine-Pouchkine wrote:
>>>>> It would certainly be nice for people looking into GlassFish
>>>>> embedded to have public JavaDoc's to
>>>>> org.glassfish.api.embedded.* and org.glassfish.api.deployment.*
>>>>> for instance.
>>>>> -Alexis
>>>>>
>>>>> On Nov 21, 2009, at 9:37, Rajiv Mordani wrote:
>>>>>
>>>>>> All,
>>>>>> During Java EE 5 / v2 days javadocs for GlassFish were
>>>>>> published at -
>>>>>>
>>>>>> https://glassfish.dev.java.net/nonav/javaee5/api/index.html
>>>>>>
>>>>>> Question - should we be publishing the APIs for the various
>>>>>> com.sun.*
>>>>>> packages that are listed here? I know that we have some new packages
>>>>>> that we should include - like hk2 but I would like for everyone to
>>>>>> review the javadocs for the com.sun.* packages and let me know if we
>>>>>> should indeed generate the javadocs for them and publish them for
>>>>>> developers. If it does not make sense for the developer, or is not a
>>>>>> committed API that a developer can use, then IMHO we should not
>>>>>> publish
>>>>>> the javadocs for the same. Please let me know if in addition to
>>>>>> these,
>>>>>> if we should generate and publish the javadocs for other packages
>>>>>> in v3,
>>>>>> including modules like metro.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> - Rajiv
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>