Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: JavaFX disappearing in Java 11 Date: Thu, 8 Mar 2018 19:28:48 -0500 Organization: Aioe.org NNTP Server Lines: 79 Message-ID: References: <64ac0595-1dec-428f-8202-107c25a90773@googlegroups.com> <1c494ba8-27fa-4584-af24-c99fa0cc9821@googlegroups.com> NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.3 Xref: csiph.com comp.lang.java.programmer:38126 On 3/8/2018 7:23 PM, Arne Vajhøj wrote: > On 3/8/2018 7:20 PM, Arne Vajhøj wrote: >> On 3/8/2018 6:57 PM, Daniele Futtorovic wrote: >>> On 2018-03-08 22:51, Arne Vajhøj wrote: >>>> On 3/8/2018 3:32 PM, Eric Douglas wrote: >>>>>                       Do end users need 2 separate installs? >>>> >>>> For development: yes. For running: not clear to me. >>> >>> I can't imagine they would possibly require an additional install for a >>> user to run JavaFX apps. Especially not when having to install the JRE >>> is already a hurdle (to Java-on-the-desktop at least) in many places. >>> >>> Note that they're talking about the JDK in that article, not the JRE. >>> End users don't (need to) install the JDK. >> >> Yes. But the same article use the term "module" in a rather >> misleading way, so I did not want to assume the article >> was 100% correct regarding it being only JDK. > > But a bit of googling indicate that indeed may be > only a developer thing. > > https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates > > > also says JDK. > > And it says: > > "With the Java Platform Module System in place since Java SE 9, it now > more viable to decouple JavaFX from the JDK, in order to make it > available as a separate download.  This will make it easier for > developers using JavaFX to have more freedom and flexibility with the > framework." > > So an Oracle SrDir product management also talking about JDK > and developers seems to be a good indication that the runtime > may still be in JRE. That blog post has a link to: http://www.oracle.com/technetwork/java/javase/javaclientroadmapupdate2018mar-4414431.pdf Which has more interesting info: Executive Summary: * The public availability of Java SE 8 updates from Oracle has been extended to January 20191. Moreover, Oracle will continue to provide consumers with updates for personal (non-corporate) use of Java SE 8 through at least the end of 2020. * Oracle will continue to support Java SE 8 Web Start applications for public and personal (non-corporate, non-commercial) use to the same dates noted above. Oracle encourages developers relying on these deployment options for the delivery of applications to consumers to migrate to other solutions. * Oracle will continue to commercially support Java Web Start on Java SE 8 for commercial use, or when used in conjunction with Oracle products that have a Web Start dependency, through at least March 2025. * As announced in 2015, Applets will continue to be supported in Java SE 8 until at least March, 2019, pending continued support by browser vendors, after which they may be removed at any time. * JavaFX new fixes will continue to be supported on Java SE 8 through March 2022 and removed from Java SE 11. * Swing and AWT will continue to be supported on Java SE 8 through at least March 2025, and on Java SE 11 (18.9 LTS) through at least September 2026. * Oracle has begun conversations with interested parties in the Java ecosystem on the stewardship of JavaFX, Swing and AWT beyond the above referenced timeframes. It sounds like the entire Java desktop is going to be separated out long term. Arne