[GRADLE-1099] StackOverflowError in idea plugin in case of circular dpenendencies Created: 09/Aug/10  Updated: 04/Jan/13  Resolved: 21/Jan/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.9.2

Type: Bug
Reporter: Steve Ebersole Assignee: Peter Niederwieser
Resolution: Fixed Votes: 5

Issue Links:
Related to GRADLE-1330 StackOverflowError in Eclipse plugin ... Resolved


Seems to be the same underlying issue as GRADLE-766 (and potentially the same underlying issues as GRADLE-715 and GRADLE-915 could be problematic here as well. Attempting to depend on FOP is a great example, since it has circular dependencies.

An project demonstrating this behavior is the jdocbook-core project at http://github.com/sebersole/jdocbook-core

Comment by Steve Ebersole [ 09/Aug/10 ]

Shoot, I cannot edit this. "Component" should have been set to the IDEA plugin.

Comment by Ashton Hepburn [ 03/Nov/10 ]

The same problem occurs with eclipseclasspath – e.g using a build.gradle that includes only a single dependency:

compile 'org.apache.xmlgraphics:batik-swing:1.7'

Posting under here as presumably the underlying issue is the same.

Comment by Gavin Mercer [ 20/Jan/11 ]

I believe I followed the instructions for contributing a patch.

http://github.com/gmercer/gradle has a branch GRADLE-1099-fix

It fixes the Steve's Idea and Ashton's Eclipse issues.

There are existing tests that verify the paths for .project/.iml creation.

Is there anything else I need to do?

Comment by Adam Murdoch [ 20/Jan/11 ]

@gavin: No, this is good. We will merge it soon. Thank you for the patch.

Comment by Strong Liu [ 22/Jan/11 ]

I can confirm this has been fixed, thanks a lot, it really helps

Generated at Wed Jun 30 11:46:52 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.