[GRADLE-2327] deal with project dependency cycles in eclipse Created: 25/May/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Related to: GRADLE-2200 I haven't found an explicit entry on that problem (I could swear it was already reported).

Eclipse plugin for certain Gradle multi-projects may generate metadata that will cause 'cycle' error in Eclipse. This may happen if project dependencies are used on given configuration. There's a way to resolve this problem in Eclipse by turning this error into a warning: Window > Preferences > Java > Compiler > Building > Build path problems > Circular dependencies = Warning.

Some options how to deal with the problem better:

1. eclipse plugin detects the cycle and generates the metadata in such a way Eclipse is happy. This requires changing the eclipse plugin quite a bit to potentially create multiple Eclipse project per single Gradle project.
2. eclipse plugin detects the cycle and automatically configures the workspace to 'warn' in case of cycles. This requires us to start generating/modelling the eclipse workspace which we don't do at the moment.
3. eclipse plugin detects the cycle and prints a detailed warning to the console explaining how to configure eclipse (or with a link to wiki/user guide, etc.)

I'd suggest to do #3 for the time being because it is cheap, risk-free and gets us closer to #1 and #2 anyway (because we would have to implement the 'cycle detection' that is needed for every option).

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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:18:53 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.