Re: [cross-project-issues-dev] e(fx)clipse participating in Mars release
I suppose all this means that no bundle with javafx dependencies can
resolve or run without this specific org.eclipse.fx.javafx bundle being
present. Again, it's none of my personal business, but if this is
indeed the only solution, would Orbit be a better host for such a thing?
org.eclipse.fx.javafx and org.eclipse.fx.osgi have to be in your runtime.
what I infer from your detailed elaboration (thanks for bringing light into the darkness) is that it would make no sense at all to separate org.eclipse.fx.javafx from org.eclipse.fx.osgi, because without the org.eclipse.fx.osgi fragment the org.eclipse.javafx bundle would be useless at runtime.
Nevertheless, couldn't it be an option to have both within Orbit? From a (simrel) participant client's perspective this could make things easier (but probably only if these bundle would then also be provided by some +0 component).
Dr. Alexander Nyßen
Telefon: +49 (0) 231 / 98 60-210
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 / 17396743
Am Brambusch 15-24
Amtsgericht Dortmund, HRB 20621
Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus
Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus
Description: Message signed with OpenPGP using GPGMail