Den tor. 27. sep. 2018 kl. 22:38 skrev Jan Tosovsky :
> On 2018-09-27 Sverre Moe wrote:
> > Den tor. 27. sep. 2018 kl. 20:06 skrev Johan Vos >:
> >
> > > 3. Stick with an LTS release and get commercial support to get updates
> > >
> > Thanks. Option 3 looks very interesting. It would allow us to
On 2018-09-27 Sverre Moe wrote:
> Den tor. 27. sep. 2018 kl. 20:06 skrev Johan Vos :
>
> > > We would probably target the Java 11 because it is LTS. Changes to JDK
> > > will be backported up to september 2023 by the community. If we are
> > > interested in getting updates on OpenJFX also we
Den tor. 27. sep. 2018 kl. 20:06 skrev Johan Vos :
> We would probably target the Java 11 because it is LTS. Changes to JDK will
>> be backported up to september 2023 by the community. If we are interested
>> in getting updates on OpenJFX also we would then need to always upgrade
>> it.
>> I
This was discussed on the list earlier this week, and the current
proposal is to support OpenJFX N on JDK N-1 or later [1].
As part of a follow-on discussion, it was suggested that we might avoid
eagerly breaking JDK N-2 unless/until there is something we need from
JDK N-1 that makes breaking
>
> How can we continue to upgrade to newer OpenJFX as time goes by. Will the
> later OpenJFX 13+ work with JDK 11 or is it just "FX N run JDK N-1" (one
> version backward support)?
>
There is a separate thread about this:
On tor. 27. sep. 2018 kl. 18:18 wrote Kevin Rushforth <
kevin.rushfo...@oracle.com>:
>
> I missed seeing the swing exception in your earlier message. Yes, the
Swing issue is a known problem in openjfx11, JDK-8210759 [1], and is
documented in the release notes [2].
>
> It will be fixed in openjfx12
