[
https://jira.codehaus.org/browse/MJAVADOC-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332206#comment-332206
]
Jörg Hohwiller commented on MJAVADOC-308:
-----------------------------------------
It is getting even more insane. I figured out what is the mattering difference
of "mvn javadoc:javadoc" - it ignores the configuration of the javadoc-plugin
from the pom as this is inside the maven-site-plugin configuration.
So I removed this option:
<maxmemory>1800m</maxmemory>
and it works fine even with "mvn site". The same effect if I call javadoc tool
manually from commandline: with more memory (-J-Xmx1800m) I get the error -
without the heap option I get no error.
So this is something the oracle javadoc developers should explain to use. Is
there something in the code like:
if (isLotsOfMemoryLeft()) {
throw new OutOfMemoryError();
}
> OutOfMemoryError
> ----------------
>
> Key: MJAVADOC-308
> URL: https://jira.codehaus.org/browse/MJAVADOC-308
> 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: http://www.atlassian.com/software/jira
