Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Unexplained dependency cycle

Unexplained dependency cycle [message #249966]

Mon, 03 December 2007 15:21

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

In a project I'm working on we're seeing some unexplained (to us)
dependency cycles when trying to build/export our app.
They look similar to this:

A cycle was detected when generating the classpath
com.company.core_1.0.0, org.eclipse.jdt_3.3.0.v20070607-1300,
org.eclipse.ui.cheatsheets_3.3.0.v20070507, com.company.core_1.0.0

When we remove org.eclipse.jdt from the com.company.core dependencies,
this error goes away. And that’s fine right now since com.company.core
doesn’t actually depend on org.eclipse.jdt, but I’m still very curious
where this cycle is coming from. I can’t for the life of me figure out
how org.eclipse.ui.cheatsheets ends up depending on our com.company.core
plugin.

Any insight? Any reference material we need to brush up on about this?

TIA,
Eric

Re: Unexplained dependency cycle [message #249970 is a reply to message #249966]

Mon, 03 December 2007 15:33

Eclipse User

Originally posted by: zx.us.ibm.com

If you look at the Plug-in Dependencies view and at the current state,
do you see anything there that would cause the cycle?

Cheers,

~ Chris

Re: Unexplained dependency cycle [message #249974 is a reply to message #249970]

Mon, 03 December 2007 22:09

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Chris Aniszczyk wrote:
> If you look at the Plug-in Dependencies view and at the current state,
> do you see anything there that would cause the cycle?

No, I didn't spot anything there; but I'll admit that I'm not 100% sure
I am interpreting that view correctly (although it seems pretty obvious).
As I said, I really don't understand how an org.eclipse plugin can be
depending on one of our plugins. Is that what the error is trying to
tell me?

"A cycle was detected when generating the classpath
com.company.core_1.0.0, org.eclipse.jdt_3.3.0.v20070607-1300,
org.eclipse.ui.cheatsheets_3.3.0.v20070507, com.company.core_1.0.0"

Eric

Re: Unexplained dependency cycle [message #249993 is a reply to message #249966]

Tue, 04 December 2007 17:13

Eclipse User

I suppose that you have a fragment for the org.eclipse.jdt plugin (or
for some other Eclipse plugin) that depends on your com.company.core plugin.

Snjeza

Eric Rizzo wrote:
> In a project I'm working on we're seeing some unexplained (to us)
> dependency cycles when trying to build/export our app.
> They look similar to this:
>
> A cycle was detected when generating the classpath
> com.company.core_1.0.0, org.eclipse.jdt_3.3.0.v20070607-1300,
> org.eclipse.ui.cheatsheets_3.3.0.v20070507, com.company.core_1.0.0
>
> When we remove org.eclipse.jdt from the com.company.core dependencies,
> this error goes away. And that’s fine right now since com.company.core
> doesn’t actually depend on org.eclipse.jdt, but I’m still very curious
> where this cycle is coming from. I can’t for the life of me figure out
> how org.eclipse.ui.cheatsheets ends up depending on our com.company.core
> plugin.
>
> Any insight? Any reference material we need to brush up on about this?
>
> TIA,
> Eric

Re: Unexplained dependency cycle [message #250012 is a reply to message #249993]

Wed, 05 December 2007 09:57

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Snjezana Peco wrote:
> I suppose that you have a fragment for the org.eclipse.jdt plugin (or
> for some other Eclipse plugin) that depends on your com.company.core
> plugin.

Thanks for the lead - it would definitely explain the situation.
Unfortunately, I looked at our fragments (we only have a couple) and
none of them specify any org.eclipse plugins as their host; they are
only hosted by our own plugins.

Eric

> Eric Rizzo wrote:
>> In a project I'm working on we're seeing some unexplained (to us)
>> dependency cycles when trying to build/export our app.
>> They look similar to this:
>>
>> A cycle was detected when generating the classpath
>> com.company.core_1.0.0, org.eclipse.jdt_3.3.0.v20070607-1300,
>> org.eclipse.ui.cheatsheets_3.3.0.v20070507, com.company.core_1.0.0
>>
>> When we remove org.eclipse.jdt from the com.company.core dependencies,
>> this error goes away. And that’s fine right now since
>> com.company.core doesn’t actually depend on org.eclipse.jdt, but I’m
>> still very curious where this cycle is coming from. I can’t for the
>> life of me figure out how org.eclipse.ui.cheatsheets ends up depending
>> on our com.company.core plugin.
>>
>> Any insight? Any reference material we need to brush up on about this?
>>
>> TIA,
>> Eric

Previous Topic:	findVariable() within breakpointHit inconsistency
Next Topic:	NullPointerException in SourceTypeConverter.parseMemberValue

Goto Forum:

-=] Back to Top [=-

Current Time: Wed May 07 00:25:37 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter