I can't tell from this stack trace what exactly you're doing, but
normally such a thing would only happen while checking for updates. Is
that what you were doing? Controlling what's in Window -> Preferences
-> Install/Update -> Available Software Sites should help eliminate the
offensive upd
Ed,
Thanks for your suggestion. I updated the Java version to the latest 1.8
update and still receive the same error.
Any ideas why an rcp installation would reference a p2.index file? Is there
any way to "clean out" a specific reference to that file from an existing rcp
installation?
Ti