Re: [osgi-dev] Eclipse Extension-points and EMF in OSGI

[Tim Ward via osgi-dev]

I would expect that Mark Hoffman or Jürgen Albert might have some useful 
pointers, I’m pretty sure that they’re heavy users of EMF.

Best Regards,

Tim

> On 9 Aug 2018, at 09:20, Alain Picard via osgi-dev  
> wrote:
> 
> Scott,
> 
> I noticed the split of the o.e.core.runtime and am already using the 
> o.e.equinox.common + supplement and running some stuff like that with Felix. 
> But that part doesn't include of the support for extension points that is in 
> the other "half", hence my question.
> 
> Alain
> 
> 
> On Thu, Aug 9, 2018 at 12:18 AM Scott Lewis via osgi-dev 
> mailto:osgi-dev@mail.osgi.org>> wrote:
> IOn 8/8/2018 7:43 AM, Alain Picard via osgi-dev wrote:
> > Working through our move from RCP to a generic OSGI solution, and I am 
> > stuck with a couple of questions.
> >
> > There was an issue a while ago for EMF that resulted in a generation 
> > setting to support generic OSGI frameworks and not only 
> > Eclipse/Equinox. But the resulting bundles still have plugin.xml and 
> > expose extension points. My understanding is that this part of Eclipse 
> > is not covered in the portable part of o.e.core.runtime. We also have 
> > a number of our own extension-points, some that we have already 
> > converted and others that are still around.
> >
> > So anyone has successfully used EMF and/or Extension points outside of 
> > a full Eclipse environment?
> 
> Yes wrt extension registry/extension points.
> 
> o.e.core.runtime is a split package, split between bundles 
> o.e.equinox.common and o.e.equinox.registry
> 
> I'm not sure of the justification for split packages, but I think it was 
> done to maintain backward compatibility in eclipse plugins.
> 
> The version I used was a few years ago, but at that time these two 
> bundles...along with equinox...would run the extension registry (i.e. 
> process extension points/extensions on startup).  AFAIK that's still the 
> case.
> 
> If you want to use a framework other than equinox, I know for certain 
> that o.e.equinox.common works just fine on Felix...as long as one also 
> includes this bundle [1].
> 
> I don't think EMF requires anything in addition to o.e.equinox.common 
> and o.e.equinox.registry but I'm not completely sure about that.
> 
> Scott
> 
> [1] org.eclipse.equinox.supplement  - available via equinox or maven central
> 
> 
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org 
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Eclipse Extension-points and EMF in OSGI

[Alain Picard via osgi-dev]

Scott,

I noticed the split of the o.e.core.runtime and am already using the
o.e.equinox.common + supplement and running some stuff like that with
Felix. But that part doesn't include of the support for extension points
that is in the other "half", hence my question.

Alain


On Thu, Aug 9, 2018 at 12:18 AM Scott Lewis via osgi-dev <
osgi-dev@mail.osgi.org> wrote:

> IOn 8/8/2018 7:43 AM, Alain Picard via osgi-dev wrote:
> > Working through our move from RCP to a generic OSGI solution, and I am
> > stuck with a couple of questions.
> >
> > There was an issue a while ago for EMF that resulted in a generation
> > setting to support generic OSGI frameworks and not only
> > Eclipse/Equinox. But the resulting bundles still have plugin.xml and
> > expose extension points. My understanding is that this part of Eclipse
> > is not covered in the portable part of o.e.core.runtime. We also have
> > a number of our own extension-points, some that we have already
> > converted and others that are still around.
> >
> > So anyone has successfully used EMF and/or Extension points outside of
> > a full Eclipse environment?
>
> Yes wrt extension registry/extension points.
>
> o.e.core.runtime is a split package, split between bundles
> o.e.equinox.common and o.e.equinox.registry
>
> I'm not sure of the justification for split packages, but I think it was
> done to maintain backward compatibility in eclipse plugins.
>
> The version I used was a few years ago, but at that time these two
> bundles...along with equinox...would run the extension registry (i.e.
> process extension points/extensions on startup).  AFAIK that's still the
> case.
>
> If you want to use a framework other than equinox, I know for certain
> that o.e.equinox.common works just fine on Felix...as long as one also
> includes this bundle [1].
>
> I don't think EMF requires anything in addition to o.e.equinox.common
> and o.e.equinox.registry but I'm not completely sure about that.
>
> Scott
>
> [1] org.eclipse.equinox.supplement  - available via equinox or maven
> central
>
>
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Eclipse Extension-points and EMF in OSGI

[Scott Lewis via osgi-dev]

IOn 8/8/2018 7:43 AM, Alain Picard via osgi-dev wrote:
Working through our move from RCP to a generic OSGI solution, and I am 
stuck with a couple of questions.


There was an issue a while ago for EMF that resulted in a generation 
setting to support generic OSGI frameworks and not only 
Eclipse/Equinox. But the resulting bundles still have plugin.xml and 
expose extension points. My understanding is that this part of Eclipse 
is not covered in the portable part of o.e.core.runtime. We also have 
a number of our own extension-points, some that we have already 
converted and others that are still around.


So anyone has successfully used EMF and/or Extension points outside of 
a full Eclipse environment?


Yes wrt extension registry/extension points.

o.e.core.runtime is a split package, split between bundles 
o.e.equinox.common and o.e.equinox.registry


I'm not sure of the justification for split packages, but I think it was 
done to maintain backward compatibility in eclipse plugins.


The version I used was a few years ago, but at that time these two 
bundles...along with equinox...would run the extension registry (i.e. 
process extension points/extensions on startup).  AFAIK that's still the 
case.


If you want to use a framework other than equinox, I know for certain 
that o.e.equinox.common works just fine on Felix...as long as one also 
includes this bundle [1].


I don't think EMF requires anything in addition to o.e.equinox.common 
and o.e.equinox.registry but I'm not completely sure about that.


Scott

[1] org.eclipse.equinox.supplement  - available via equinox or maven central


___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

[osgi-dev] Eclipse Extension-points and EMF in OSGI

[Alain Picard via osgi-dev]

Working through our move from RCP to a generic OSGI solution, and I am
stuck with a couple of questions.

There was an issue a while ago for EMF that resulted in a generation
setting to support generic OSGI frameworks and not only Eclipse/Equinox.
But the resulting bundles still have plugin.xml and expose extension
points. My understanding is that this part of Eclipse is not covered in the
portable part of o.e.core.runtime. We also have a number of our own
extension-points, some that we have already converted and others that are
still around.

So anyone has successfully used EMF and/or Extension points outside of a
full Eclipse environment?

Thanks
Alain
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev