In this case, I'm not doinganything multi-project. I've yet to get the one project really in shape yet... :) But I can certainly see where that might catch you.
On Thu, 10 Mar 2005 15:17:14 -0500, James Mitchell <[EMAIL PROTECTED]> wrote: > Just to throw out one possibility. I "accidentally" (wink) forgot to > exclude my project/build dir that I called multiproject:site from and was > getting OutOfMemory exceptions because it was recursing into itself. Adding > the following to project.properties fixed it. > > maven.multiproject.excludes = build/* > > That me be totally unrelated, but I just thought I would pipe in here. > > -- > James Mitchell > Software Engineer / Open Source Evangelist > EdgeTech, Inc. > 678.910.8017 > AIM: jmitchtx > > ----- Original Message ----- > From: "Brett Porter" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: "Maven Users List" <[email protected]> > Sent: Thursday, March 10, 2005 2:58 PM > Subject: Re: OutOfMemory errors in site > > >I think maven.javadoc.maxmemory=1024M is correct. > > Do you perhaps need to fork as well? > > > > > > On Thu, 10 Mar 2005 13:56:12 -0600, Mykel Alvis <[EMAIL PROTECTED]> > > wrote: > >> I'm sorry. I also meant to say that I've looked across the archives > >> of the mailing list at > >> > >> http://java2.5341.com/bbs/s.jsp?q=maven+%2Bjavadoc+%2Boutofmemoryerror > >> > >> but I failed to acquire anything that you haven't told me already. I > >> also tried > >> > >> maven.javadoc.maxmemory=1024M > >> > >> but that didn't do anything, either. > >> > >> Also, I tried specifying MAVEN_OPTS=-Xmx1024M (and 512M) and running > >> the site generation from the command line with no further success. > >> > >> > >> On Thu, 10 Mar 2005 13:50:49 -0600, Mykel Alvis <[EMAIL PROTECTED]> > >> wrote: > >> > OK. I tried this. > >> > > >> > maven.javadoc.additionalparam=-Xmx1024M > >> > > >> > in project.properties. And it still continues to give a > >> > [javadoc] javadoc: java.lang.OutOfMemoryError: Please increase > >> > memory. > >> > [javadoc] 1 error > >> > [javadoc] For example, on the Sun Classic or HotSpot VMs, add the > >> > option - > >> > Xmx > >> > [javadoc] such as -J-Xmx32m. > >> > > >> > BUILD FAILED > >> > File...... C:\Documents and > >> > Settings\ebsmxa\.maven\cache\maven-jellydoc-plugin > >> > .3.1\plugin.jelly > >> > Element... j:include > >> > Line...... 53 > >> > Column.... 73 > >> > > >> > Did I do something wrong? I got absolutely no farther than before. > >> > Granted there are a couple thousand source files in the application, > >> > but I didn't think generating javadocs was THAT memory intensive. > >> > > >> > Any further advice? > >> > > >> > > >> > On Sun, 6 Mar 2005 14:18:33 -0800, Brett Porter > >> > <[EMAIL PROTECTED]> wrote: > >> > > use maven.javadoc.additionalparam > >> > > > >> > > http://maven.apache.org/reference/plugins/javadoc/properties.html > >> > > > >> > > There is more discussion in the archives. > >> > > > >> > > Cheers, > >> > > Brett > >> > > > >> > > > >> > > On Sun, 6 Mar 2005 16:16:25 -0600, Mykel Alvis > >> > > <[EMAIL PROTECTED]> wrote: > >> > > > Using maven 1.0.2, jellydoc-1.3.1 and site-1.6, I run out of memory > >> > > > generating the site every time. The project has a very large > >> > > > number > >> > > > of source files (over 3000) and a large quantity of code for most > >> > > > of > >> > > > those files. > >> > > > > >> > > > I've looked around the web quite a bit but haven't found the answer > >> > > > to my issue. > >> > > > > >> > > > The error I get is : > >> > > > [javadoc] javadoc: java.lang.OutOfMemoryError: Please increase > >> > > > memory. > >> > > > [javadoc] 1 error > >> > > > [javadoc] For example, on the Sun Classic or HotSpot VMs, add > >> > > > the > >> > > > option -J-Xmx > >> > > > [javadoc] such as -J-Xmx32m. > >> > > > > >> > > > I'm currently running with MavenIDE and Eclipse 3.0.1 but it occurs > >> > > > outside of the ide as well. I've set my MAVEN_OPTS options in both > >> > > > the command line and ide startups to have several values, from 256M > >> > > > up > >> > > > to 1024M of heap, but to no avail. I noticed on the JIRA at > >> > > > CodeHaus > >> > > > that several people had a similar issue, and that there might be a > >> > > > leak in the doc generation, but it appears to have been smoothed > >> > > > over, > >> > > > ignored, or fixed and I don't have the fix. > >> > > > > >> > > > Is there something I can do to mitigate this issue? > >> > > > > >> > > > Mykel > >> > > > > >> > > > --------------------------------------------------------------------- > >> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > > > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > >> > > > > >> > > > >> > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
