Re: [jgit-dev] Bunch of "A cycle was detected" errors after pulling JGit

[Tomasz Zarna <tzarna@xxxxxxxxx>]

> - I didn't find a way to create them again

For me it's enough to restart Eclipse to see the cycles again. Luckily
I found a workaround (at least working for me): close and reopen
org.eclipse.jgit.ui. Works like a charm.

> Probably using the target
> platform defined in org.eclipse.egit.target would fix this.

I'm using egit-3.7.target and it doesn't seem to help a bit.

I'm on M20121003-1000 + JGit/EGit 2.4.0.201302140025.

Cheers,
Tomek

On Wed, Feb 20, 2013 at 9:01 AM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
> 2013/2/19 Robin Rosenberg <robin.rosenberg@xxxxxxxxxx>
>>
>> I did a fresh clone today and I get the cycle errors.
>>
>> Could it be that our test bundles contain the same package names
>> and therefore confused the dependency logic?
>
>
> I tried the following:
> - installed fresh Eclipse SDK 4.3 M5
> - installed egit/jgit 2.4-SNAPSHOT and jgit dependencies using p2f file
> - cloned a fresh jgit into a new workspace
> - -> no cycles
> - uninstalled egit/jgit 2.4 SNAPSHOT and installed egit/jgit 2.3 release
> - -> build cycles
> - found some missing version boundaries in dependencies of
> org.eclipse.jgit.ant.test
> - fixing them doesn't fix the cycles
> - closed all jgit projects and reopened them
> - -> cycles are gone
> - I didn't find a way to create them again
>
> really strange, it seems the resolution logic mixes 2.4 and 2.3 versions
> coming
> from installed jgit with those available as source. Probably using the
> target
> platform defined in org.eclipse.egit.target would fix this.
>
> Which Eclipse version are you using ?
>
> --
> Matthias