Just because eclipse might not like it does not make it broken ;)
On Thursday, March 31, 2011, at 05:14 am, Max Rydahl Andersen wrote:
>> 2)Eclipse
>> the configuration files generated by gradle are totally wrong, but I
>> could fix them by hand.
>> Now Eclipse refuses to compile the project as there's a circular
>> dependency: the testsuite from hibernate-core depends on the
>> hibernate-testing module, which in turn depends on hibernate-core.
>
> This was intentional. Both gradle and intellij can handle this. I asked
> max and he said that such a set up was in some way workable.
I said it was probably possibly to workaround/hack, but I did not at all
recommend it.
It's a broken setup IMO.
> I dont understand what is so foreign about this "circularity". Look at
> it at the task level. You compile hibernate-core/src/main; you compile
> hibernate- testing/src/main; you compile hibernate-core/src/test. Yes
> there is "circularity" if you look strictly at this in terms of modules.
> But in terms of tasks and source sets there is not.
There is of project dependencies - which is the level eclipse is working
on.
Just because the compile setup is possible doesn't make it right IMO.
/max
http://about.me/maxandersen
---
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org