How to find out which location from the target file provided a plug-in?

[vogella]

Frequently I have to search for "why do we have two versions of this plug-in" problem. Most recently a client had two versions of OSGi (one from an EGit addional library feature and its update site and one from the platform feature. This client used slicer.

My current "process" is to comment out parts of the target platform, reload it and see if it is gone. This is time consuming, as the resolving of the target platform is still relatively slow. Is there an easier way to find out where a plug-in is coming from?

[merks]

This sounds like a question/discussion not an issue. When you checkmark show content it shows the answer to your question in the tree on the first tab doesn’t it?

[vogella]

This is a discussion, is it not? URL for me is #897

When you checkmark show content it shows the answer to your question in the tree on the first tab doesn’t it?

It shows the general available content from this location, not the included plug-ins based on your configuration. So while is is helpful to identify the potential source, it does not answer the question where does "xyz" come from. For example 20 location may have the OSGi bundle included but the features I added from these locations in 18 cases do not include this one.

[merks]

Sorry, it's misleading on a phone...

I'm not sure what specifically you are referring to in your comment. Here it's showing the 14 bundles that come from EMF and not the huge number available at the site:

[vogella]

Thanks, definitely better than my currently approach, but for bigger sites and , this still requires a lot of checking with standard target editor with scrolling.
E.g nebula with 282 and Sep release with 530 entries.

The Repository Explorer looks way better for this task, as it have a filter box, especially with the expert mode which shows technical names. Thanks for that.

Still not the a direct way to answer: "Where does plug-in x come from"? but an easier way to answer "Lets see which locations contain the plug-in X" and once we have check enough locations we can also see where x is coming from.

[HannesWell]

Besides what has been said, in the Content Tab of the Target Editor you can also Group by Location:

Furthermore if you want to know the dependents/dependencies of a Plugin, the Plug-ins Dependencies view also shows them both to you:

You can open it from the Dependencies Tab in the MANIFEST.MF Editor or directly by clicking on the Focus button ("magnifying glass") in the view.
On a Feature level the Features view also shows inter-Feature dependencies.

[vogella]

Besides what has been said, in the Content Tab of the Target Editor you can also Group by Location:

Thank you @HannesWell, this is exactly what I needed. Thanks a bunch, also to @merks for the advice and help