maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <>
Subject [jira] (MJAVADOC-308) OutOfMemoryError
Date Sun, 01 Sep 2013 14:09:52 GMT


Jörg Hohwiller commented on MJAVADOC-308:

JIRA is converting asterik into markup - I wanted to say that I deleted all java files with
Vertical in the name (2 files) and all with Horizontal (2 files).

Further, the problem can not be reproduced if I can "mvn javadoc:javadoc" with all files present.
So I assume that there is something wrong in maven-javadoc-plugin. Where can I find the files
"@options" and "@packages" so I can see if maven generated these wrong somehow?

[ERROR] javadoc: error - java.lang.OutOfMemoryError: Please increase memory.
[ERROR] For example, on the JDK Classic or HotSpot VMs, add the option -J-Xmx
[ERROR] such as -J-Xmx32m.
[ERROR] Command line was: "C:\Program Files\Java\jdk1.7.0_25\jre\..\bin\javadoc.
exe" -J-Xmx1800m @options @packages
> OutOfMemoryError
> ----------------
>                 Key: MJAVADOC-308
>                 URL:
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6.1, 2.7
>         Environment: Maven 3 on MacOS 10.6, Maven 3 on Hudson on Windows
>            Reporter: Pieter
> I have a 12 module project (+parent) containing not really much code (140 classes). When
running Maven site on this project, it fails with an OutOfMemoryError. When I run the javadoc
plugin with a reportset containing javadoc, test-javadoc and aggregate is runs well with a
maximum heap size of 512M. When I run it with a reportset containing javadoc, test-javadoc
and test-aggregate also. But when I add all 4 reports to my report set, I get an OutOfMemoryError,
even when setting the maximum heap size to 1.5G. Just before the error occurs I see my heap
usage growing rapidly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message