Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] What policy w.r.t. javafx package imports?

Hi,

I'm fine with contributing our runtime-feature as +1 and the IDE-Feature
as +3.

Tom

On 20.08.14 14:06, Alexander Nyßen wrote:
> I added the following efxclipse.b3aggrcon to my local simrel build for
> testing purposes and validated that with the e(fx)clipse runtime feature
> in place, those GEF4 features depending on JavaFX could now indeed be
> resolved (i.e. the aggregation could be validated). 
> 
> <?xml version="1.0" encoding="ASCII"?>
> <aggregator:Contribution xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI";
> xmlns:aggregator="http://www.eclipse.org/b3/2011/aggregator/1.1.0";
> description="JavaFX Tooling for Eclipse" label="e(fx)clipse">
>   <repositories
> location="http://download.eclipse.org/efxclipse/runtime-released/1.0.0/site";>
>     <features name="org.eclipse.fx.core.feature.feature.group"
> versionRange="[1.0.0,2.0.0]">
>    
>   <categories href="simrel.b3aggr#//@customCategories[identifier='General%20Purpose%20Tools']"/>
>     </features>
>   </repositories>
> </aggregator:Contribution>
> 
> As such, the presence of the e(fx)clipse runtime feature would be
> sufficient to resolve all javafx package import problems. Nevertheless,
> if e(fx)clipse joins as a +3 component, GEF as a +1 component would have
> 9 out of 14 features depending (directly or indirectly) on a +3
> component, only because we specify some javafx package imports. While +3
> probably is a good choice for e(fx)clipse from an IDE tooling
> perspective, I somehow have the impression that this is not appropriate
> for its runtime, which only makes the javafx classes available on the
> osgi classpath.
> 
> Cheers
> Alexander
> 
> Am 20.08.2014 um 10:48 schrieb Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx
> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>:
> 
>> Hi,
>>
>> We'll join as +3 but I can not promise we manage to contribute to M1
>> already because I need to make myself familiar with the process, ... .
>>
>> Tom
>>
>> On 20.08.14 10:28, Alexander Nyßen wrote:
>>> Tom,
>>>
>>> at what offset can we expect the e(fx)clipse contribution? Will you
>>> contribute something to M1?
>>>
>>> Cheers
>>> Alexander
>>>
>>> Am 18.08.2014 um 21:59 schrieb Alexander Nyßen
>>> <Alexander.Nyssen@xxxxxxxxx <mailto:Alexander.Nyssen@xxxxxxxxx>
>>> <mailto:Alexander.Nyssen@xxxxxxxxx>>:
>>>
>>>> I temporarily disabled all GEF4 features that (directly or indirectly)
>>>> depend on JavaFX. I do not know what is the intended offset of
>>>> e(fx)clipse, but unless we find out how to provide these dependencies
>>>> (i.e. jfxrt.jar in case of Java7, jfxswt.jar in case of Java8) to B3
>>>> directly (i.e. jfxrt.jar in case of Java7, jfxswt.jar in case of
>>>> Java8) we will have to re-enable them after e(fx)clipse has joined
>>>> (and potentially update our contribution).
>>>>
>>>> Cheers
>>>> Alexander
>>>>
>>>> Am 18.08.2014 um 21:43 schrieb Alexander Nyßen
>>>> <alexander.nyssen@xxxxxxxxx <mailto:alexander.nyssen@xxxxxxxxx>
>>>> <mailto:alexander.nyssen@xxxxxxxxx>>:
>>>>
>>>>> 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
>>>>> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>
>>>>> <mailto:tom.schindl@xxxxxxxxxxxxxxx>>:
>>>>>
>>>>>> 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
>>>>>> <david_williams@xxxxxxxxxx <mailto:david_williams@xxxxxxxxxx>
>>>>>> <mailto:david_williams@xxxxxxxxxx>>:
>>>>>>
>>>>>>> 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 <alexander.nyssen@xxxxxxxxx
>>>>>>> <mailto:alexander.nyssen@xxxxxxxxx>
>>>>>>> <mailto:alexander.nyssen@xxxxxxxxx>>
>>>>>>> To:        Cross project issues
>>>>>>> <cross-project-issues-dev@xxxxxxxxxxx
>>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>>,
>>>>>>> Date:        08/18/2014 12:58 PM
>>>>>>> Subject:        [cross-project-issues-dev] What policy w.r.t.
>>>>>>> javafx package        imports?
>>>>>>> Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx
>>>>>>> <mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx>
>>>>>>> <mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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 <http://www.itemis.de>_
>>>>>>> <http://www.itemis.de/>_
>>>>>>> __alexander.nyssen@xxxxxxxxx <http://itemis.de>_
>>>>>>> <mailto: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" deleted by David M
>>>>>>> Williams/Raleigh/IBM] _______________________________________________
>>>>>>> cross-project-issues-dev mailing list
>>>>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>>>> 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
>>>>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>>>> 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
>>>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>>> 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 <http://www.itemis.de/>
>>>>> alexander.nyssen@xxxxxxxxx <mailto:alexander.nyssen@xxxxxxxxx>
>>>>> <mailto: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
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cross-project-issues-dev mailing list
>>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>>>> 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 <http://www.itemis.de/>
>>>> alexander.nyssen@xxxxxxxxx <mailto:alexander.nyssen@xxxxxxxxx>
>>>> <mailto: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
>>>>
>>>>
>>>
>>> --
>>> 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 <mailto:alexander.nyssen@xxxxxxxxx>
>>> <mailto: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
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@xxxxxxxxxxx
>>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>>> 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
>> cross-project-issues-dev@xxxxxxxxxxx
>> <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>> 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 
> alexander.nyssen@xxxxxxxxx <mailto: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
> 
> 
> 
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 



Back to the top