Jurgen, This looks fantastic. Just out of curiosity, have you used it with CDO ?
Alain On Thu, Aug 9, 2018 at 10:11 AM Jürgen Albert via osgi-dev < [email protected]> wrote: > It appears that we are too stupid to configure the project properly. You > can get started with this: > https://gitlab.com/gecko.io/geckoEMF/wikis/Get-started > > > Am 09/08/2018 um 14:54 schrieb Alain Picard: > > > On Thu, Aug 9, 2018 at 8:45 AM Jürgen Albert via osgi-dev < > [email protected]> wrote: > >> Hi Alain, >> >> EMF does work without extension points, but in its current state needs >> manual registration of you EPackages. >> > Ok that is the interesting part. > > The OSGi Compatibility option in the genmodel only defines the >> org.eclipse.core.runtime as optional, which dues does not really solve >> anything. >> > Agreed, not much. > >> >> We have an extension for EMF that solves this issue. You can have EMF >> with any framework you like and without extension points. Have a look here: >> https://gitlab.com/gecko.io/geckoEMF >> > Gitlab is reporting an error " An error occurred while loading commit > signature" and not getting that error with the other gecko.io project. > > >> >> If you have any questions, feel free to ask. >> >> Jürgen. >> >> Am 09/08/2018 um 11:12 schrieb Tim Ward: >> >> >> >> Begin forwarded message: >> >> *From: *Tim Ward <[email protected]> >> *Subject: **Re: [osgi-dev] Eclipse Extension-points and EMF in OSGI* >> *Date: *9 August 2018 at 10:02:50 BST >> *To: *Alain Picard <[email protected]>, OSGi Developer Mail List < >> [email protected]> >> *Cc: *Scott Lewis <[email protected]> >> >> 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 < >> [email protected]> 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 < >> [email protected]> 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 >>> [email protected] >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> >> >> >> -- >> Jürgen Albert >> Geschäftsführer >> >> Data In Motion Consulting GmbH (haftungsbeschränkt) >> >> Kahlaische Str. 4 >> 07745 Jena >> >> Mobil: 0157-72521634 >> E-Mail: [email protected] >> Web: www.datainmotion.de >> >> XING: https://www.xing.com/profile/Juergen_Albert5 >> >> Rechtliches >> >> Jena HBR 513025 >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > > -- > Jürgen Albert > Geschäftsführer > > Data In Motion Consulting GmbH (haftungsbeschränkt) > > Kahlaische Str. 4 > 07745 Jena > > Mobil: 0157-72521634 > E-Mail: [email protected] > Web: www.datainmotion.de > > XING: https://www.xing.com/profile/Juergen_Albert5 > > Rechtliches > > Jena HBR 513025 > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
