| [cross-project-issues-dev] What policy w.r.t. javafx package imports? |
| Hi all, as some of the new GEF4 bundles we want to include with Mars specify javafx package imports (so far without version constraints), I was wondering what general policy we want to follow to ensure such kind of bundles can be properly resolved. Should we rely on the e(fx)clipse runtime bundles/fragments (org.eclipse.javafx and org.eclipse.fx.osgi), i.e. re-bundle them in our features or specify feature-dependencies to the enclosing e(fx)clipse runtime feature, or is there another intended way (it seems, e(fx)clipse has not announced its participation)? Cheers Alexander
--
Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 http://www.itemis.de alexander.nyssen@xxxxxxxxx itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: 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 |
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail