The following comment has been added to this issue:
Author: Joakim Erdfelt
Created: Mon, 20 Oct 2003 10:14 AM
Body:
We are seeing a host of OutOfMemoryErrors with many maven-reports, including javadoc
and junit.
Example of our environment.
(host name and project name neutered, due to corporate concerns)
[EMAIL PROTECTED]:project-foo]$ sloccount src src-test
SLOC Directory SLOC-by-Language (Sorted)
490497 src java=490497
75257 src-test java=75257
[EMAIL PROTECTED]:project-foo]$ find src -name "*.java" | wc -l
1151
[EMAIL PROTECTED]:project-foo]$ find src-test -name "*.java" | wc -l
430
[EMAIL PROTECTED]:project-foo]$ echo $MAVEN_OPTS
-Xmx2048m
This is a large solaris box we are compiling on, with 28GB of RAM, and over 900GB of
free disk space. So RAM and Disk Space is not a problem.
Yet, we cannot run maven against this modestly sized project with the following
reports turned on.
All of these plugins will cause an OutOfMemoryError (or StackOverflowError) with 2GB
of RAM allocated to the project.
* maven-javadoc-plugin - 1.3
* maven-junit-report-plugin - 1.3
* maven-linkcheck-plugin - 1.1
* maven-tasklist-plugin - 2.2
We also have a project of 4,166 classes (single WAR file) that can only be compiled,
jar'd, and deployed.
I've been working on a plugin updates / patches / replacements for large projects.
(Already have a patch into jcoverage for large sets of classes under windows.)
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-711
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-711
Summary: java.lang.OutOfMemoryError when running maven
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-javadoc
plugin-junit-report
Fix Fors:
1.1
Assignee:
Reporter:
Created: Fri, 22 Aug 2003 5:01 AM
Updated: Sun, 24 Aug 2003 9:21 PM
Description:
When running maven plugins (specifically javadoc and junit), we're now getting
OutOfMemoryErrors. This was not a problem earlier, presumably because the codebase was
smaller.
Running these exact same tasks using a plain ant script does not cause any problems,
so it must be something with maven.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]