[
https://jira.codehaus.org/browse/MJAVADOC-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332192#comment-332192
]
Jörg Hohwiller commented on MJAVADOC-308:
-----------------------------------------
I am facing the same problem since a longer while and investigated on this
problem.
Could you please re-open.
Facts:
* I am facing this problem on Windows7 x64
* The problem occurs only with java1.7 and not with java1.6. As I dropped
compatibility for 1.6 in my code I am now unable to build my maven site
regularly.
* I already filed an issue at Oracles java issue tracker but it seems only
reproduce-able with maven and mvn javadoc:aggregate is working. Like Sun also
Oracle continues the strategy that new issues are hidden unless they are
confirmed to be visible for the public. Hence I can not give a link (Mail
conversation with oracle was "Java bug submitted 2013-02-15 15:40:54.55").
* My project is entirely OSS so you can try it yourself:
https://github.com/m-m-m/mmm
Please let me know if there is something I should test in particular.
> 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
