In a sense isn’t this really a flavor of incompatible libraries? Say for example junit 3/4/5 with each needing separate instances of the dependencies being defined and added in some way?
Or maybe should ask how was it handle switching from JavaFX 1(JavaFX script version) vs JavaFX 2 (redone was java based versions) previously? Given the recent different java EE in play maybe something similar there with new/legacy/version specific. Can always mark some elements as @depricated to provide some time to prune eventually. Could some form of hint/tip be added towards migration to openjfx version sort of like some places where new java features are suggested like string/expression case statements, diamond operators, lambdas, etc.? Heh...at some point is the Netbeans UI going to be redone in jfx ;-) ? Eric Bresie [email protected] > On August 25, 2019 at 10:28:31 AM CDT, Vlad Palnik <[email protected]> wrote: > NetBeans needs to support any Java version that has not reached EOL. Most > production environments use LTS versions and as long as they are are > supported by Oracle they need to be supported by NB. > > On Sun, Aug 25, 2019, 8:21 AM Chuck Davis <[email protected]> wrote: > > > At the pace Java is moving no reasonable person would expect ANYTHING based > > upon Java to forever be backwardly compatible. > > > > In my not so humble opinion we need a clean break occasionally where we say > > the current Java environment requires new capabilities in the IDE and > > version x.x will no longer work on Java versions less than x.x. > > > > For people still stuck on Java8 they should be able to indefinitely work > > with Netbeans 11.1 and lower. For people progressing with newer versions > > of Java (my Linux distro keeps Java up to date automatically) the IDE needs > > to drop old features and add new Java features as Java changes. It's going > > to require backward compatibility to be broken but that does not mean the > > version that worked at that version of Java should be discontinued at least > > for a number of years -- it should still be available to those working with > > older versions of Java. Enterprises update much more slowly than the Java > > world progresses. > > > > So I vote for NB 12 to drop support for Java 11 and lower to concentrate on > > incorporating the new features of Java and not be hassled by backward > > compatibility. Those still on Java 11 and below can happily keep on using > > NB 11.1 indefinitely. > > > > Just my $.02 and I am well aware it is a minority opinion. > > > > On Sun, Aug 25, 2019 at 2:42 AM Geertjan Wielenga <[email protected]> > > wrote: > > > > > Hi all, > > > > > > What to do with JavaFX and OpenJFX? > > > > > > Should we continue making projects and samples available for JDK 8 JavaFX > > > in the New Project dialog, because some users may be using JDK 8, or > > should > > > we only have projects and samples for OpenJFX in the New Project dialog? > > > > > > The full situation is described in detail here in a new blog entry I > > wrote > > > a few minutes ago: > > > > > > https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx > > > > > > Thanks, > > > > > > Gj > > > > >
