Yep, that was the problem. I got it to work specifying maxmemory of
2048m (just started at the top) and then I decided to see if I could
make it work with something smaller and discovered something funny. In
genesis we specify 512 (not 512m). When I initially saw this I thought
it must default to megabytes but it turns out it really defaults to
bytes since I could get it to work with a local setting of 512m.
Thanks,
Joe
Jason Dillon wrote:
The m-javadoc-plugin spawns a javadoc process, so the heap settings for
mvn aren't going to get used at all there. You must configure the heap
size in the plugins configuration.
--jason
On Oct 21, 2008, at 6:33 PM, Joe Bohn wrote:
Hmmm ... good point. I was just setting it in maven opts (xMx). I'll
try setting it on the plugin config also and see if that helps.
Thanks,
Joe
Jason Dillon wrote:
Are you setting the plugin's maxmemory or just mvn's max?
--jason
On Oct 21, 2008, at 3:30 AM, Joe Bohn wrote:
I think it was Jarek that first raised the alert that the javadoc
available for the server on our website is still pointing to 2.0.1.
I took a look into generating some updated javadoc for 2.1.3 but
encountered a problem and wonder if anybody has any ideas.
While attempting to build the javadoc using the maven javadoc plugin
I continually get a OutOfMemoryErrors. This persists even if I set
-Xmx to the max (2048).
After some google searches I stumbled on this and was hopeful it
might be culprit [1] given that we have several "<attribute" entries
in comments that javadoc might attempt to process as address tags.
However even after encoding the "<" to < for each "<attribute" in
a comment I still encountered the same problem.
Any ideas?
There are some directions on generating the javadoc located here if
you want to give it a shot yourself:
https://svn.apache.org/repos/asf/geronimo/site/trunk/JavaDoc.readme
Perhaps this has something to do with the java version on my mac.
[1]
http://mail-archives.apache.org/mod_mbox/maven-users/200712.mbox/[EMAIL PROTECTED]
and the referenced bug
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5082928
Thanks,
Joe
