[jira] Commented: (IVY-595) Out of memory/Stack overflow for new highly coupled project.

["Jan Koops (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582939#action_12582939 ] 

Jan Koops commented on IVY-595:
-------------------------------

We have exactly the same environment (monolithic project  now split up into about 100 modules) and we've had the same problem with 2.0.0-alpha-2.
Now since 2.0.0-beta-1 the problem is gone, so I think this issue can be closed.

> Out of memory/Stack overflow for new highly coupled project.
> ------------------------------------------------------------
>
>                 Key: IVY-595
>                 URL: https://issues.apache.org/jira/browse/IVY-595
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha-2
>         Environment: OSX 10.4.10, Java 1.5.0_07
>            Reporter: Colin Fleming
>             Fix For: 2.0
>
>         Attachments: boom.tbz2
>
>
> We're trying to convert an existing large project to use Ivy. It's an OSGi project, so it's already sorted into modules (bundles) and Ivy makes a lot of sense. The problem is that the project has a lot of modules (83) and since we're moving from a monolithic project it's massively interdependent, there are circular dependencies all through it. When we try to run an ivy:buildlist on the whole project, it just barfs with a java.lang.OutOfMemoryError: Java heap space. If we try to run the buildlist giving it a single module as a root it gives a java.lang.StackOverflowError.
> Attached are the project ivy.xml files required to reproduce the problem, as well as a simple build.xml with two targets to reproduce the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.