[GRADLE-715] Circular Runtime Project Dependencies cause stack overflow Created: 22/Oct/09 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.8 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Steve Appling | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Issue Links: |
|
||||||||
| Description |
|
Circular project dependencies cause a stack overflow exception. While circular compile dependencies are not useful, they should fail more gracefully (like circular task dependencies do). While generally indicative of a design problem, circular runtime (configuration) dependencies should be supported. This generally just needs to result in all the projects being on the classpath. We have a circular dependency which built and ran with our system under ant and we are having problems migrating this to gradle. The compile dependency was broken using reflection, but both projects needed to be on the runtime classpath for it to work. We can't accomplish this with gradle now. |
| Comments |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Benjamin Muschko [ 10/Feb/17 ] |
|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |