=>From: Rachel Greenham <[EMAIL PROTECTED]>
=>...
=>I can't create a Javadoc of my library! I get out of memory errors. The
=>computer has loads of memory left over.
"I can't be overdrawn -- I still have checks left!" :-)
=>Any ideas what I can do about this?
The <A HREF="http://java.sun.com/products/jdk/javadoc/faq.html#memory>Javadoq
FAQ</A> notes:
Javadoc does take a lot of memory because (unlike javac) it must
simultaneously load all the classes being documented[...]
The <A
HREF="http://java.sun.com/products/jdk/1.3/docs/tooldocs/solaris/javadoc.html#javadocoptions">Javadoc
docs</A> give you the option to increase memory allocation (in fact,
it's the example for the "-J" option):
% javadoc -J-Xms32m -J-Xmx32m com.mypackage
to set the initial and maximum heap sizes, respectively.
I've used these args myself to produce documentation for all the core
classes, and a few extensions, in one swell foop.
d.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
