[
http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100688
]
Nicolas Cazottes commented on MNG-3073:
---------------------------------------
I actually set the memory configuration I mentionned through the environment
variable MAVEN_OPTS.
My point is that the solution to increase the memory endless is not a good one
because I may be at some time faced to a limit of my computer memory size if my
number of projects increases to 1000.
Forking the compiler should be an option but I think it will increase the
compilation time which is currently 12min average. I will try it to see.
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3
> levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of
> each project increases as well.
> What we are faced to is that we constantly need to increase the memory size
> allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters :
> -Xmx900m -Xms128m for our compilation with the following command line : mvn
> install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
