On Tue, Sep 18, 2012 at 11:00 AM, Mickael Istria <mistria@redhat.com> wrote:

Hi all,

While I'm trying to see what can be cleaned in parent pom, I've made some investigations around XulRunner. My starting points were those 2 issues:
https://issues.jboss.org/browse/JBIDE-12455 (existing profiles for macosx, to run tests using a 32-bits JVM apparently because of XulRunner)
https://issues.jboss.org/browse/JBIDE-5418 (general issue about XulRunner and MacOSX Cocoa 64-bits)

I've asked Eclipse forums on this topic and it appears that SWT ships its own version of XulRunner as part of the SWT platform-specific fragments: http://www.eclipse.org/forums/index.php/mv/msg/377759/915713/#msg_915713

Then I'm wondering why use a copy of XulRunner? Is it still necessary? If SWT has a XulRunner for Cocoa 64bits, why do we have specific profiles to use 32bits?

SWT ships libraries for XULRunner support only, it does not ship XULRunner itself.