Unfortunately, the
nasty episode from around a year ago is still source of a lot of annoyances in using the (otherwise great) Eclipse platform.
I do embrace the concept of loosely coupled components instead of giant balls of library-bundling, but i must admit, it has its advantages.
On openSUSE 11.4 after some updating, XulRunner screwed up content assyst/auto completion again, this time i used another workaround, namely exactly
specifying the XulRunner path in the eclipse.ini configuration -vmargs:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-1.9.2/xulrunner
Indigo seems to play nice with this version, at least, until now.
Geen opmerkingen:
Een reactie posten