Community
Participate
Working Groups
Build Identifier: 20111103 nightly build XULRunner can not be loaded in Eclipse 3.7. When config added in eclipse.ini, the XULRunner related function will cause eclipse crush. Reproducible: Always Steps to Reproduce: 1. Create a new workspace by eclipse 3.7 2. Create a Web Client with Service Project, and create a RUIhandler 3. Close the workspace, and config the XULRunner in eclipse.ini 4. Reopen the workspace, change the build in browser to XULRunner. There will be an alert popup indicate that "The application has been updated, but your version of SQLite is too old and the application cannot run". 5. Then the eclipse got error and crushed.
Which version of XULRunner are you using? I found that the 3.6.x versions work, but the newer versions (6, 7, ...) do not work in SWT.
I was able to reproduce this if I surrounded the path to XULRunner with quotes. If I remove the quotes then it works (spaces in the path still work). BAD: -Dorg.eclipse.swt.browser.XULRunnerPath="C:\xulrunner folder" GOOD: -Dorg.eclipse.swt.browser.XULRunnerPath=C:\xulrunner folder
Justin, Thanks a lot for digging out the root cause. Xin, please try Justin's suggestion: remove the quote in XULRunner path.
Hi Justin & Jimmy Thanks so much for your information. I've tried your suggestions. Firstly I verified the quotes issue, my test environment did not added quotes in eclipse.ini before for there is no space in my path. Then I tried the XULRunner 3.6.23 and 6.0. [For 3.6.23] The same problem as this bug described. [For 6.0] The error message show can not find the XULRunner, the same info as no XULRunner configured. I also reproduced in other two machines, Jimmy is now looking into it.
SWT does not support 6.0 so there is no need to try that - it will not work. Can you attach your eclipse.ini file?
Hi Justin, I think this is an issue described here: Bug 349837 - Incompatibility between WebKit and XULRunner's sqlite. Still don't have ideas about it.
Created attachment 206636 [details] eclipse.ini Hi Justin, Here is my eclipse.ini for eclipse 3.7. For Jimmy's comments. I also found something to prove it. 1.XULRunner works well in eclipse 3.6 now, which wont' have a Webkit&XULRunner conflict problem. 2.In previous version(about 3 weeks ago) of EDT in eclipse 3.7, the XULRunner works well.
For this can not be reproduced in all environments and the bug of SWT, down the severity to normal
Setting this to P3 because this is not a common scenario.
Brenda ran into the same issue described using XULRunner 19 and eclipse 37 and have the safari installed on this window machine. I hope the end user will not have both safari and xulrunner installed together as a common scenario.
how about XULRUnner 3.6.24?
deferred
Saul, I'm not sure if we have a place where this can be documented?
If this only happens with XULRunner 1.9, I think we should close this defect as no plan to fix. All of our testing has been done with 3.6.2x, and 1.9 is probably too old.
Eric in comment #4 seems to indicate it doesn't work for XULRunner 3.6.23 either on eclipse 37 with safari installed
Thanks Jing. Keeping as deferred. Saul, please try to comment on this somewhere for .7.
