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]

Reply via email to