[jbosstools-dev] Do we still need our own XulRunner?

[Mickael Istria]

On 09/18/2012 03:44 PM, Yahor Radtsevich wrote:
> Hi,
>
> On Tue, Sep 18, 2012 at 11:00 AM, Mickael Istria <mistria at redhat.com 
> <mailto:mistria at 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.

Thanks for this clarification.

>     Any help is welcome, and even more that help, some tests on Cocoa
>     64 bits!
>
> We can not run any XULRunner/VPE tests on Cocoa 64-bit, unless we 
> build/find a stable XULRunner 1.9.x for it.

I've searched for an existing XulRunner build for 1.9.x Cocoa 64 bits, 
in vain.
We should try to create our own build, it would be a one-time effort 
that would improve JBT on Mac 64 bits.
Continuing discussion on https://issues.jboss.org/browse/JBIDE-5418

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20120918/fa33f6b8/attachment.html