CODEWITHSUNDEEP
eclipsepluginsideosgicircular-dependency
amarillion
amarillion

Reputation: 24907

Untangling dependency cycles in eclipse

I'm trying to export a plug-in feature as webstart in eclipse. After setting up feature.xml, and running the export wizard, when I click finish I get the following error:

A cycle was detected when generating the classpath org.pathvisio.core_2.0.11, org.pathvisio.batik.codec_1.7.0, org.pathvisio.batik.transcoder_1.7.0, org.pathvisio.pdftranscoder_1.7.0, pvplugins-bridgedbSettings_1.0.0.201106291012, org.pathvisio.core_2.0.11.

The trouble is, I have no idea where this cycle is exactly. So my question is: how do I find out which plug-in is causing the cyclic dependency? Are there any tools to help analyse dependency problems?

Upvotes: 1

Views: 3484

Answers (2)

searching9x
searching9x

Reputation: 1605

A cycle was detected when generating the classpath

It means that somewhere you have a plugin A requiring plugin B and plugin B requiring plugin C. plugin C requiring plugin A.

Find and fix this!

Upvotes: 0

Tonny Madsen
Tonny Madsen

Reputation: 12718

The message above lists the exact plug-ins that makes up the elements of the cycle. It is not a single plug-in that is responsible for the cycle; it is the listed set of plug-ins... So org.pathvisio.core has a dependency on org.pathvisio.batik.codec which has a dependency on...

When you try to understand the dependencies, remember to include the installed fragments in the calculations :-)

To visualize the dependencies, I usually open the PDE editor of one of the plug-ins, go to the "Dependencies" page, in the botton-right section you have a number of tools that can help you - in this case primary "Look for cycles in the dependency graph".

Upvotes: 4

Related Questions