Would that mean I have to specify dependencies to e(fx)clipse or would b3 resolve this implicitly? Up to now, my bundles only specify javafx package imports (including imports to javafx.embed.swt)...
Cheers Alexander Am 18.08.2014 um 21:40 schrieb Tom Schindl <[email protected]>: > a) e(fx)clipse just released 1.0 > b) the bundles required only depend on equinox >= Luna > > So no matter if we (efxclipse) are on the Mars release GEF4 should be fine! > > Tom > > Von meinem iPhone gesendet > > Am 18.08.2014 um 21:22 schrieb David M Williams <[email protected]>: > >> And, in the mean time, it seems your current contribution won't "aggregate" >> (and mentions missing things somehow related to "fx". Can you disable those >> features for now? >> >> For the record, if the "required project" did not participate, you can >> "include" their features in yours, but, only from their latest released >> version (if there is one ... and if there is not a released version, then >> you could not do it). >> >> Thanks, >> >> >> >> >> From: Alexander Nyßen <[email protected]> >> To: Cross project issues <[email protected]>, >> Date: 08/18/2014 12:58 PM >> Subject: [cross-project-issues-dev] What policy w.r.t. javafx package >> imports? >> Sent by: [email protected] >> >> >> >> 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 >> [email protected] >> >> 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" deleted by David M Williams/Raleigh/IBM] >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- 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 [email protected] 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
