<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
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:<br>
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-12455">https://issues.jboss.org/browse/JBIDE-12455</a> (existing profiles for
macosx, to run tests using a 32-bits JVM apparently because of
XulRunner)<br>
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-5418">https://issues.jboss.org/browse/JBIDE-5418</a> (general issue about
XulRunner and MacOSX Cocoa 64-bits)<br>
<br>
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:
<a class="moz-txt-link-freetext" href="http://www.eclipse.org/forums/index.php/mv/msg/377759/915713/#msg_915713">http://www.eclipse.org/forums/index.php/mv/msg/377759/915713/#msg_915713</a><br>
<br>
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?<br>
Any help is welcome, and even more that help, some tests on Cocoa 64
bits!<br>
<br>
Cheers,<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>