Hi,
Thanks for the tip. Javadocs files are down considerably by excluding
"com.*" and "org.*" packages.
The issue now is posting it to java.net. It takes forever publishing
the javadocs using CVS. "cvs add" and "cvs commit" stall and after a
few hours, "Broken Pipe" message displayed. Unfortunately, this is the
only way to publish to java.net site.
I spoke to Kohsuke and he suggested to publish javadocs to another
external location (not java.net). It'll makes future publishing easier
and browsing will be faster since it's not via "https" and "java.net".
So I have requested the external DNS name, "javadoc.glassfish.org".
It will take few days to get this setup.
Sorry that it's taking this long.
Jane
Bill Shannon wrote:
> Jerome Dochez wrote:
>> it seems to me that you are aggregating the javadocs for the entire
>> source tree of v3 which might not be that interesting. Probably
>> something like this :
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-javadoc-plugin</artifactId>
>> <configuration>
>> <excludePackageNames>com.*:org.*</excludePackageNames>
>> </configuration>
>> </plugin>
>
> Right, I'm *sure* you don't want the javadocs from every class in the
> product. Start with the javax.* classes and add whatever other classes
> Jerome says are equivalent to public classes in the previous release.
>
> Maybe we want a separate set of javadocs containing the exported APIs
> for each module.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>