It's possible that you can fix this by starting like:
$ eclipse -clean
According to the Tasks->Running Eclipse,
Cleans cached data used by the OSGi
framework and Eclipse runtime. Try to
run Eclipse once with this option if
you observe startup errors after
install, update, or using a shared
configuration.
If that doesn't work, well,
the Eclipse ui contributions are in XML, originally all in some plugin.xml
, which was kind of cool because the UI could then be built up on a fast scan without loading any java from all those plugins. I believe they have evolved a more complicated modularity API in recent years but you may be able to find the guilty file by grepping *.xml and *.properties for Spket.IDE
. There is a level of indirection through the .properties
files because strings are usually externalized for translation.
Still, you might get somewhere with something like:
grep Spket.IDE `find . -name \*.xml -o -name \*.properties`