Community
Participate
Working Groups
in m2 - open a plugin editor (mine was on a bundle from the target) - on the Dependencies tab, expand the Dependency Analysis section - click on the Show dependent plugins... link - notice the Plugin Dependencies view opens - the problem is that in my system the view is empty. - right click and select Focus on... - enter the name of the plugin you were editing - notice that now the view has lots of great content The ideal workflow would be if you are editing the Foo bundle and select "show dependencies", the view that opens would show the dependencies without further action.
This only happens for non-workspace bundles. Looking at a fix.
Created attachment 133696 [details] Patch Reason for the bug is that the code is looking for a project (getProject()), which is not there for non workspace bundles. Instead it should be looking for a plugin, as is done in doFindLoops() method of the same class.
We can review this patch for RC1.
*** Bug 262329 has been marked as a duplicate of this bug. ***
*** Bug 256282 has been marked as a duplicate of this bug. ***
done. > 20090507 Thanks for the patch Deepak!
Does not work for me. The view is empty. I see getPlugin().getId() returning null in this case. The plugin.xml editor does not seem to work at all for external bundles... all text fields are empty on the overview page, for example.
Suggest to revert/defer.
Works if you open the manifest editor from the Plugins view... if you open from the navigator, it does not... hmmm. OK.
Verified.
I see how it doesn't work now. If you open it from the navigator and JUST have the plugin model loaded (ie., not the MANIFEST.MF in any of the tabs), it will fail.
