Andrew Overholt wrote:
[1]
"Could not open the editor: The editor class could not be instantiated. This
usually indicates a missing no-arg constructor or that the editor's class name
was mistyped in plugin.xml."
java.lang.NullPointerException
at
org.eclipse.core.internal.runtime.Activator.getURLConverter(Activator.java:313)
at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:164)
at
org.eclipse.linuxtools.systemtap.ui.editor.SystemtapEditor.<init>(SystemtapEditor.java:52
I believe two things are going on here.
1) Some badly written validation code is not taking account of a NPE
when completion/stp_completion.properties cannot be found. This contains
all of the completion proposals that the System Tap editor can work with
in the current release. The NPE checking is a bug that needs to be fixed
in the first place.And ...
2) That somehow completion/stp_completion.properties is not in your
plug-in deployment, or where the plug-in can find it.
I'm still hacking on the editor, and I've never deployed this plug-in
beyond the PDE and I'm guessing paths are just not working outside of
that environment. An instant workaround would be to place the
completion/stp_completion.properties manually if you have deployed the
plug-in. Anyway two bugs there ....
Sorry for the pain ;)
Regards
Phil
_______________________________________________
linux-distros-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/linux-distros-dev
