[GRADLE-1580] Generating eclipse files for Gradle itself creates cyclic project dependencies between core and coreImpl Created: 01/Jun/11  Updated: 04/Jan/13  Resolved: 05/Jul/11

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

Type: Bug
Reporter: Carsten Mjartan Assignee: Szczepan Faber
Resolution: Fixed Votes: 0


 Description   

There is a test dependency between "core" and "coreImpl" which itself depends on "core", and since Eclipse does not differenciate between main and test dependencies, it shows a cyclic dependency and projects cannot be built.



 Comments   
Comment by Adam Murdoch [ 06/Jul/11 ]

I don't think we should close this until we've done something to stop the problem coming back. This is too easy to break again. It would be nice to have an automated test of some kind which fails when there are cycles in the eclipse projects. There are probably some other inspections we want to do for the IDE metadata.

Comment by Szczepan Faber [ 07/Jul/11 ]

>I don't think we should close this until we've done something to stop the problem coming back.

Possibly, but it's not an incremental approach I'd keep this closed and open a separate ticket for it that could potentially have a different priority. In general, I might even not open a new ticket but wait for a user to open it if some user finds it important enough. Looks like it already happened, though: GRADLE-1581

>This is too easy to break again. It would be nice to have an automated test of some kind which fails when there are cycles in the eclipse projects. There are probably some other inspections we want to do for the IDE metadata.

Absolutely. Again, they should be different tickets possibly with various different priorities.

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