[jbosstools-dev] XULRunner 1.9.2 XPCOM is different for each platform

[Maksim Areshkau]

.
Andersen Max wrote:
> what can I do to get my jboss tool checkout having a working VPE right now ? 
>   
https://svn.jboss.org/repos/jbosstools/workspace/mareshkau/xulrunner-1.9.2
> do we have a bug open somewhere for the different APIs ? This must surely be some big oversight?
>   
I have commented this one, https://jira.jboss.org/browse/JBIDE-6429
For now this problems resolved by using interfaces es common for all 
platforms.
> /max
>
> On Jun 16, 2010, at 23:14, Maxim Areshkau wrote:
>
>   
>> Hi,
>> see attachment.
>> We have extracted common interfaces for all platforms and placed as source files into org,mozilla.xpcom plugin https://svn.jboss.org/repos/jbosstools/workspace/mareshkau/xulrunner-1.9.2/org.mozilla.xpcom/
>> So Now we have working VPE under Mac OS X, Linux and Windows. But Junit still crashes see this one https://bugs.eclipse.org/bugs/show_bug.cgi?id=315588
>> Before this I have tried to use jars from linux sdk under mac and it caused a crash of eclipse(https://bugs.eclipse.org/bugs/show_bug.cgi?id=316872). I think because have occurred some native calls which not supported for osx.
>>
>>
>> 2010/6/16 Denis Golovin <dgolovin at exadel.com>
>> I've seen this in IRC log
>>
>> 12:49:55 AM) maxandersen: mareshkau: soon means when ? :)
>> (12:50:08 AM) mareshkau: I think by the end of this week
>> (12:50:32 AM) maxandersen: will we need to split out the jar plugin in os specific osgi bundles?
>> (12:54:02 AM) mareshkau: We have java sources from xpcom, so #1 we will try to create our own xpcom.jar with common api jar-s for all platforms.
>> (12:54:02 AM) mareshkau: #2 if #1 will not work, than split out the jar plugin in os specific osgi bundles
>> (12:56:22 AM) maxandersen: why not just do the split ?
>> (12:59:02 AM) mareshkau: because api will be different and somebody possibly can use windows function and broke compilation
>>
>> Why wouldn't we just create fragments for xpcom plugin with platform related code and include it to xulrunner feature instead of trying to fix something in our code?
>> What is different in API?
>>
>> Denis
>>
>>
>>
>> -- 
>> Maksim Areshkau
>> <api-difference.html>
>>     
>
>