That's pretty easy to answer. Felix by default exports all standard Java SE packages. JavaFX is not part of Java SE, it is an extension that is only available on a subset of Java implementations.
Neil On 12 Dec 2017 2:56 pm, "Chuck Davis" <cjgun...@gmail.com> wrote: > Hi Kerry: > > Thanks for the note. Old indeed. I don't remember anything I learned > from that project (though I did keep the modules). I did get it to work by > including the module somebody mentioned. It seems so easy, looking at that > module, I can't understand why Felix doesn't do the export for JavaFX so > that it's not even an issue -- at least an option that can be turned on or > off, installed or uninstalled or some such and stop the necessity of all > the work-arounds on which developers are having to waste their time. > > If I revisit OSGi I'll take a look at your project if Felix hasn't fixed > the issue yet at the time. > > Thanks. > > CD > > On 12/12/2017 05:19 AM, Kerry wrote: > >> Hi Chuck, >> >> I realise that this is a response to an old message of yours but I have a >> GitHub project that may be of interest to you that brings OSGi to JavaFx. >> >> https://github.com/jtkb/osgifx >> >> It aims to be simpler than Drombler and is agnostic to the OSGi >> implementation. It is still a work in progress but check the examples and >> integration-test modules to see how to use it. I have currently tested it >> with Apache karaf which obviously used Apache Felix but plan to add tests >> for other implementations too. >> >> If you try it out any comments you have or improvements are welcome. Any >> issues also just ask. I'm in the process of improving the documentation at >> the moment. >> >> Kerry >> >> Sent from BlueMail >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > >
