On Sun, 29 Sep 2019 at 11:50, Matthias Bläsing <[email protected]> wrote: > > Am Sonntag, den 29.09.2019, 11:38 +0100 schrieb Neil C Smith: > > On Sun, 29 Sep 2019, 11:24 Chuck Davis, <[email protected]> wrote: > > > > > It would certainly be nice if FX > > > were still part of the JDK. > > > > > > > It never really was! ;-) > > > > And currently it is easier than ever to pull it in and distribute it > with your application (that is if you don't mind GPLv2-CPE as license). ... > For netbeans the only thing preventing its use is the same, that > prevents bundling the JDK:
There's a subtle difference though. The JDK is considered a "platform" dependency, a definition that gets somewhat more dubious by the day. So we can't bundle it, but we can link to it! JavaFX was shipped with *some* JDK's. Let's not start with the annoyance of things that assumed all of them! :-) In such circumstances, it might be arguable that we could treat JavaFX as a platform dependency. That argument is now more dubious. Even if I think it's a positive move for JavaFX itself. So, my comment was not entirely off-topic in the sense that this might have impact on whether any such effort to develop a JavaFX window manager could at all be developed here as opposed to somewhere else. I'm potentially interested in seeing one, although I'd also be interested in seeing one based on HTML4J. Like Matthias, I'd like to see some changes in how Apache considers GPLv2-CPE and also the nature of platform dependencies, or things are likely to get more complicated for us in a changing Java ecosystem. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
