You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/30 01:58:55 UTC

[jira] Closed: (MNG-3073) Memory Leak in maven2 for multiproject

     [ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-3073.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.2.x)

> Memory Leak in maven2 for multiproject
> --------------------------------------
>
>                 Key: MNG-3073
>                 URL: http://jira.codehaus.org/browse/MNG-3073
>             Project: Maven 2 & 3
>          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