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

what can I do to get my jboss tool checkout having a working VPE right now ?

do we have a bug open somewhere for the different APIs ? This must surely be some big oversight?

/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.... > 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(a)exadel.com&gt; > 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> >

On Jun 17, 2010, at 13:36, Maksim Areshkau wrote: > . > 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. > I mean - do we know about a bug/discussion on eclipse.org or mozilla ?

/max >> /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.... >>> 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&lt;dgolovin(a)exadel.com&gt; >>> 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> >>> >>> >> >> >

I found that last changes in VPE just slay all VPE related tests because of xulrunner plugin versions range is started from 1.9.2.0 but there is no xulrunner feature for it. I decreased it to 1.9.1.0 and can confirm it healed tests at least under gtk.linux.x86.

I don't think it is good to change vpe code ahead of providing xulrunner plug-ins for all platforms supported by JBossTools/JBDS without backward compatibility.

I'm not sure it is going to work for mac, I'll check it as soon as I get version built with uberbuilder. Denis On 06/17/2010 06:00 AM, Maksim Areshkau wrote: > On 6/17/10 2:55 PM, Andersen Max wrote: >> On Jun 17, 2010, at 13:36, Maksim Areshkau wrote: >> >>> . >>> 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. >> I mean - do we know about a bug/discussion on eclipse.org or mozilla ? > I haven't find in firefox bugzilla, so I have created one > https://bugzilla.mozilla.org/show_bug.cgi?id=572677 >> /max >> >>>> /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.... >>>>> >>>>> 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&lt;dgolovin(a)exadel.com&gt; >>>>> 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> >>>>> >>>> >