Re: Later OpenJFX Compatibilty with JDK 11 LTS
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 deliver a > > stable application on the current LTS while the same time get updates on > > JavaFX. > > If I understand correctly, there will be 4th option in near future: > 4. Bundle module based app with JDK modules you need > > From that moment you are becoming independent on any future FX and JDK > releases. Especially handy if your app doesn't evolve much and it is > distributed in controlled environment (several users within company). > Unless your app becomes famous, I don't think it will attract attackers to > employ any vulnerabilities found in those older versions as time goes. > > Jan > > Being a SCADA application, keeping it stable and secure is very important, even though our application is not famous or known beyond the industry we deliver it to. /Sverre
RE: Later OpenJFX Compatibilty with JDK 11 LTS
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 would then need to > > > always upgrade it. > > > I reckon there will not be a OpenJFX 11 LTS. > > > > Actually, there is. See > > https://gluonhq.com/javafx-11-release-and-support-plans/ for commercial > > support for JavaFX 11 LTS. > > > > Basically, you have 3 options: > > 1. Move along with the latest and greatest JavaFX releases (free) > > 2. Stick with a given release (free, unsupported) > > 3. Stick with an LTS release and get commercial support to get updates > > > Thanks. Option 3 looks very interesting. It would allow us to deliver a > stable application on the current LTS while the same time get updates on > JavaFX. If I understand correctly, there will be 4th option in near future: 4. Bundle module based app with JDK modules you need >From that moment you are becoming independent on any future FX and JDK >releases. Especially handy if your app doesn't evolve much and it is >distributed in controlled environment (several users within company). Unless >your app becomes famous, I don't think it will attract attackers to employ any >vulnerabilities found in those older versions as time goes. Jan
Re: Later OpenJFX Compatibilty with JDK 11 LTS
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 reckon there will not be a OpenJFX 11 LTS. >> > > Actually, there is. See > https://gluonhq.com/javafx-11-release-and-support-plans/ for commercial > support for JavaFX 11 LTS. > > Basically, you have 3 options: > 1. Move along with the latest and greatest JavaFX releases (free) > 2. Stick with a given release (free, unsupported) > 3. Stick with an LTS release and get commercial support to get updates > > - Johan > Thanks. Option 3 looks very interesting. It would allow us to deliver a stable application on the current LTS while the same time get updates on JavaFX. I have not seen Oracle offering an JavaFX 11 LTS, just the JDK 11 LTS. Is Gluon the only one with a JavaFX 11 LTS? /Sverre
Re: Later OpenJFX Compatibilty with JDK 11 LTS
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 it necessary. Requiring later versions of FX to run on JDK 11 LTS would mean, for example, that OpenJFX 14 wouldn't be able to use language features from JDK 12 or JDK 13, which seems a bit restrictive. -- Kevin [1] http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-September/022538.html On 9/27/2018 10:16 AM, Sverre Moe wrote: > 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)? > > 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 reckon there will not be a OpenJFX 11 LTS. > > /Sverre
Re: Later OpenJFX Compatibilty with JDK 11 LTS
> > 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: http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-September/022527.html It seems we are moving to a consensus where we use existing JDK versions as long as there are no new API's/VM changes that really benefit JavaFX, however the "guaranteed" required version for JavaFX N would be Java N or Java N-1. > 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 reckon there will not be a OpenJFX 11 LTS. > Actually, there is. See https://gluonhq.com/javafx-11-release-and-support-plans/ for commercial support for JavaFX 11 LTS. Basically, you have 3 options: 1. Move along with the latest and greatest JavaFX releases (free) 2. Stick with a given release (free, unsupported) 3. Stick with an LTS release and get commercial support to get updates - Johan
Later OpenJFX Compatibilty with JDK 11 LTS
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 just as soon as I push the fix for JDK-8210092 [3] later today (the review was just finished earlier this morning). This was one of the bugs waiting until the fix requiring JDK 11 for openjfx 12 was pushed. > > -- Kevin > > [1] https://bugs.openjdk.java.net/browse/JDK-8210759 > [2] https://github.com/javafxports/openjdk-jfx/blob/jfx-11/doc-files/release-notes-11.md#known-issues > [3] https://bugs.openjdk.java.net/browse/JDK-8210092 > On tor. 27. sep. 2018 kl. 18:50 wrote Kevin Rushforth < kevin.rushfo...@oracle.com>: > > Backporting this fix would mean an openjfx 11.x update release would stop building or running with JDK 10. Not something that would be done lightly, since it would break the "FX N runs with JDK N-1" policy we have been discussing lately. There is an easy workaround for that bug that needs to be done when running "jlink" to create your image. It's documented in the release notes. > > -- Kevin 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)? 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 reckon there will not be a OpenJFX 11 LTS. /Sverre
