Community
Participate
Working Groups
XULRunner has been deprecated by Mozilla and SWT has since (4.6) stopped making any fixes for the XULRunner support. The latest version of XULRunner supported by Eclipse/SWT 4.7 is XULR31. Default browser support available on each of the platforms: Windows: IE Linux/GTK: Webkit Mac/Cocoa: Webkit Also, please see Bug 405031 to follow ongoing work/discussion on Implementing Chromium support for SWT. This is the top level bug to capture all the tasks required to drop support for XULRunner. This can be done in steps: 1. Stop building the libraries 2. Remove the libraries from the binaries repos 3. Remove the source code
I've pushed the build file changes for Step 1. Waiting for PMC approval to continue with Steps 2 & 3.
If it's deprecated we can't support it.
I said it the other bug but we should go and do 2 and 3 .
IIRC, a long tme ago there were features in JSDT which required XULRunner and didn't work on Webkit (maybe for JavaScript debugging? Might also have been some accessibility testing features in ASDT). I might be wrong in the first place, and newer technologies like the browser's embedded debugging engines might have replaced earlier approaches. But either way, shouldn't a decision for dropping XULRunner be discussed on cross-project before we actually take steps in the code? There might be contributors willing to invest into maintaining it, if they depend on it.
(In reply to Martin Oberhuber from comment #4) > IIRC, a long tme ago there were features in JSDT which required XULRunner > and didn't work on Webkit (maybe for JavaScript debugging? Might also have > been some accessibility testing features in ASDT). > > I might be wrong in the first place, and newer technologies like the > browser's embedded debugging engines might have replaced earlier approaches. > But either way, > shouldn't a decision for dropping XULRunner be discussed on cross-project > before we actually take steps in the code? There might be contributors > willing to invest into maintaining it, if they depend on it. JSDT includes ChromeDevTools based debugger IIRC. Noone noticed/complaint about it on Linuxes even though we default to GTK3 where xulrunner is not available at all. Versions of xulrunner supported are ancient and full of security holes, I even doubt that many people have xulrunner 31 (released 3 years ago) or older to even try it. If there were people interested in investing in maintaining it they would have showed up by now, don't you think so?
All the child bugs are done. Resolve the tracker too.
Need to add this to migration guide and in N&N. Also, need to update any related documentation such as faq, etc.
(In reply to Lakshmi Shanmugam from comment #7) > Need to add this to migration guide and in N&N. Also, need to update any > related documentation such as faq, etc. Added entry to N&N - http://git.eclipse.org/c/www.eclipse.org/eclipse/news.git/commit/?id=6c5e0ef394117a485f4bd27f3e4f60dbb79c74ce Opened Bug 520495 to update the documentation.
XULRunner should remain in SWT before the Chromium available for production.. Thanks
(In reply to Missing name from comment #9) > XULRunner should remain in SWT before the Chromium available for production.. > Thanks Chromium is not a replacement for XULRunner. Webkit(1 & 2) is a replacement for XUL runner. (at least on linux). Feel free to ping me if you have questions, I'd be happy to elaborate :-).
I ran into this problem today when installing SimplicityStudio 4 from SILabs. How is it progressing?
