maven-issues mailing list archives

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

    [ https://jira.codehaus.org/browse/MJAVADOC-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332203#comment-332203
] 

Jörg Hohwiller commented on MJAVADOC-308:
-----------------------------------------

The generated files (options, packages) do not differ in a relevant way (doctitle differs)
if I use mvn javadoc:javadoc.
What else can be the difference why mvn javadoc:javadoc does not cause the problem?
                
> 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

Mime
View raw message