SWT build dependency

[steve.x.northover at oracle.com]

Sure, but if the bridge is part of SWT and joins that code base (like 
the Swing bridge), then it gets released with SWT.

Steve

On 19/10/2012 10:41 AM, Tom Schindl wrote:
> Am 19.10.12 16:28, schrieb steve.x.northover at oracle.com:
>> .. the reply in private was an accident.  Thanks for forwarding back to
>> the list.
>>
>> I'm not against contributing the code to Eclipse.org and having it in
>> SWT, just like the Swing bridge.  There are a few arguments against
>> this.  The code uses objects and frameworks that are not yet open
>> source.  It is easier to keep the code up to date when FX changes and
>> ensure that interop works from day one when FX ships rather than
>> aligning with an Eclipse release.
>>
> (I assume most people consume SWT along with Eclipse-RCP in an OSGi-Env)
>
> For people to easily consume those in their RCP application the
> following would be ideal:
> a) the jar has the OSGi-Manifest headers
> b) the OSGi-Bundle is part of the p2 repository
>
> To align it with FX rather than SWT I guess this would be possible at
> the moment someone proposes an JavaFX-Project at Eclipse.org ;-) and
> Oracles contribution to it is the SWT-FX-Bridge.
>
> The project then aligns its release schedule to the one of FX beside
> following the Eclipse-Release-train.
>
> Tom
>
>