Community
Participate
Working Groups
I think this infamous issue it resurfacing ... see for example bug 287505 and related bugs ... but this time for a pretty special case. Both Eclipse 36 and Eclipse 35 run fine on new x86 build server (that is, they come up, displaying UI, in an X Session ?if I use an IBM VM, not the default?). But, Eclipse 342 does not work. The splash screen shows up, but then ends, with a message in log about "org.eclipse.swt.SWTError: XPCOM error -2147467262" So ... I have a vague memory that for such an old level of Eclipse it _required_ to have a "lower" version of XULRunner. On old machine, We used to be able to point explicitly to an older version, using -Dorg.eclipse.swt.browser.XULRunnerPath= /shared/common/mozilla-xulrunner181-1.8.1.4-30.ppc But ... that is specific for PPC architecture (I'm assuming, from its name). So, I'm wondering if we could have a similar one for our new x86 machine? Our need for this is not huge. We only rarely need to do anything with an Eclipse at the 3.4 level ... and then it is only to run our unit tests after applying some small patch in WTP. The "UI tests" in those suites no longer run on new build machine .... but the "core" tests run fine. Jacek provided previous XULRunner 1.8.1 PPC version ... perhaps he has one handy for x86? Jacek? If there happens to be one handy in SUSE repositories, that'd be fine too ... just be sure not to "install" it in some way that would make it the default one found on the path, or something.
The only xulrunner packages in the SLES repo are 1.9.0 (not installed) and 1.9.1 (installed). I'm hoping Jacek can help us out.
XULRunner 1.9.0.x should be fine for eclipse 3.4.x. If you don't want to install the one from the SLES repository then you can just get xulrunner 1.9.0.11 for x86 from http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.0.11/runtimes/ and then point at it with -Dorg.eclipse.swt.browser.XULRunnerPath .
(In reply to comment #2) > XULRunner 1.9.0.x should be fine for eclipse 3.4.x. If you don't want to > install the one from the SLES repository then you can just get xulrunner > 1.9.0.11 for x86 from > http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.0.11/runtimes/ > and then point at it with -Dorg.eclipse.swt.browser.XULRunnerPath . I'll try this with our old builds and confirm it works as expected. I'll just "copy" (not install) runtime to /shared/common
Worked just fine. Its at times like this I think that software development is magic and that there actually is hope in the world. :)
