[GRADLE-1355] Running 'gradle eclipse' for Gradle itself does generate faulty eclipse metadata. Created: 27/Jan/11  Updated: 04/Jan/13  Resolved: 07/Feb/11

Status: Resolved
Project: Gradle
Affects Version/s: 0.9.2
Fix Version/s: 1.0-milestone-1

Type: Bug
Reporter: Hans Dockter Assignee: Peter Niederwieser
Resolution: Fixed Votes: 0


When running gradle eclipse for Gradle and import the subprojects, I get a lot of cyclic dependencies errors.

Comment by Peter Niederwieser [ 28/Jan/11 ]

I've tried to get rid of the cyclic dependencies by moving out integration tests (but not the integration test fixtures) from core into a new subproject, but I couldn't get the (whole) build running again. Someone who better understands the Gradle build will have to help me with this one.

Comment by Matthias Hryniszak [ 29/Apr/11 ]

I've just downloaded the latest sources from github, executed gradle eclipse on Gradle itself and the issue with cyclic dependencies still exists. Shouldn't we reopen this issue?

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