You can try running only the targets used for creating the Jmol.jar files instead of the targets used for creating a full buil archive.
Otherwise, there's the possibility to modify the build.xml so that javadoc can be disabled if some value is defined. There's already something like that for the translations (i18n) in other languages.
It takes a lot of time too, it's not activated by default (you have to define do.create.pot and do.create.po to true with -Ddo.create.pot=true ...). It's active on my own computer but that's because I maintain the translations and make the releases on sourceforge.

I am out of town for a long weekend and my net access is not very good, so I am not sure I can modify anything before a few days. Same for the release of 12.0.RC9...


On Fri, Apr 30, 2010 at 6:27 AM, Jonathan Gutow <gutow@uwosh.edu> wrote:
Because webexport accesses files that are distributed with Jmol, I like to test changes using a rebuilt distribution.  However,  recreating the javadocs takes a long time.  Can I create a distribution without going through the javadocs rebuild?

hmm...in the background javadoc is now giving a java.lang.OutOfMemoryError: Java heap space....That's a new one.


Jmol-developers mailing list