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).