I think that dropping the ability to compile for Java 8 should be out of question, because there is a large adoption of the platform and there are a few license free alternatives, like Amazon Corretto, so even corporate developers do not need to flee away from JDK 8 to protect the company from potential license issues. In my company we decided to go all the way to OpenJDK 11, but I do not feel this is what everybody did. And to be fair, we still compile for 8 for keeping a door open. Regarding the platform on which NB runs, it might be considered (I do not know if it has been ruled out in the past) to have an internal JDK for Netbeans, like other IDEs do. In this case, the freshest LTS platform could be a reasonable suggestion. The point that dropping Java 8 only one LTS platform would be supported is a strong one, and I think there could be a rule to state end of life for a platform after two newer LTS releases.
Michele Costabile michele.costab...@gmail.com > Il giorno 27 feb 2020, alle ore 14:00, Geertjan Wielenga > <geert...@apache.org> ha scritto: > > Well, maybe we could discontinue nb-javac from 12.0 onwards, assuming the > javac tooling by then does most/all we need, which would not mean that the > OracleLabs scenario below is impacted since that use case is unrelated to > the Java editor, which is the only place where nb-javac is relevant. I.e., > we’d still support JDK 8, just not for editing Java code in the editor. > > Feel free to shoot this down, it’s just a thought. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
