Unfortunately it is a no go to just drop in the org.eclipse.pde.runtime plug-in into 3.3.1. Too much has changed:
- the LogView implementation has moved, so you lose the Error Log.
- RegistryBrowserLabelProvider uses new 3.4 methods on org.eclipse.osgi.service.resolver.State...though I was surprised the method was not tagged with a @since ??
So my simple debugging gem will remain in my bag of tricks to help quickly diagnose a bug or evaluate to emulate a part of Eclipse where a solution is presented for a problem/flow similar to mine.
But if you are using and working on top of 3.4, get to know Alt-Shift-F1.
P.S. I have filed an enhancement (bug 226590) for the plug-in spy (patch attached for those busy PDE dudes)...I look forward to spying on those content outline pages in M7 ;-)