Oh, now I get it. So you can still compile projects with JDK 8 and use the editor, but you must run the IDE itself on JDK 14, and with no nb-javac (to make JDK 8 projects work).
That actually seems very reasonable! -- Eirik -----Original Message----- From: Geertjan Wielenga <[email protected]> Sent: Tuesday, April 28, 2020 12:29 PM To: [email protected] Subject: Re: nb-javac and the upcoming 12.0 Yes, the Java editor uses the JDK 14 javac if it runs on that JDK — even if the build of a particular project uses JDK 8 or anything else. Gj On Tue, 28 Apr 2020 at 18:25, Scott Palmer <[email protected]> wrote: > Just my 2 cents... I am all for NB having great first-class support > for development of projects that use Java 8, but I don’t care if I’m > forced to run NB itself with JDK-14. > I realize that some have projects based on the NB platform that they > want to run on Java 8. I think if you are in that situation, you have > to decide to keep with an older version of the NB platform because we > can’t hold the platform back to Java 8 compatibility forever. > > That being said, I would like to be able to change the default JDK for > projects so it is a different JDK than what NB is running on. Having > to go through most of my projects and explicitly flip them to use JDK > 8 is a minor pain, and it also makes sharing the project with a team a > little more awkward as well. They need additional configuration in NB > so the right JDK can be found and we have to share NB project files > that otherwise don’t need to go into the project’s source repo. > > What is unclear to me, and it seems I’m not alone, is if NB is running > on > JDK-14 without nb-javac, what do we miss when working on a project > that builds with JDK-8? Can the NB editor not use JDK-14’s javac even > tough the build runs with JDK-8? > > Scott > > > On Apr 28, 2020, at 10:50 AM, Geertjan Wielenga > > <[email protected]> > wrote: > > > > You're not going to find me arguing against good support for Java 8. > > However, as stated above, we anticipate that nb-javac will not be > > ready > in > > time for the 12.0 release. > > > > Gj > > > > On Tue, Apr 28, 2020 at 4:46 PM Eirik Bakke <[email protected]> wrote: > > > >>> A question is what about JDK 8. My bold suggestion would be that > >>> we > >> explicitly tell our users that they can’t use our Java Editor if > >> they’re running NetBeans on JDK 8. > >> > >> I think it's too early to drop first-class support for Java 8, for > >> the same reasons people listed in the earlier "Pull the plug from > >> Java 8 in 12.1?" thread. > >> > >> Good support for Java 8 is a feature, and an important one for an > >> IDE > that > >> is primarily associated with the Java ecosystem. > >> > >> Eirik > >> > >> -----Original Message----- > >> From: Geertjan Wielenga <[email protected]> > >> Sent: Tuesday, April 28, 2020 2:47 AM > >> To: dev <[email protected]> > >> Subject: nb-javac and the upcoming 12.0 > >> > >> Hi all, > >> > >> We’re getting close to the 12.0 release and nb-javac won’t be > >> available > at > >> the time of release. What nb-javac provides is detailed elsewhere > >> but in summary it is a fork of the javac finetuned to the Java > >> Editor in NetBeans. It can’t be donated to Apache NetBeans because > >> it is a javac > fork > >> and hence GPL licensed, so Oracle does not want to donate it and > >> Apache projects can’t be released with it. > >> > >> Ultimately, we’d like to drop the need for nb-javac completely. > >> That > will > >> simplify things a lot. Plus, that is increasingly possible because > >> from > JDK > >> 9 onwards we’re able to use the javac from the JDK that NetBeans > >> runs on for the same purposes as nb-javac. > >> > >> And we’ve (especially Jan Lahoda) been enhancing Apache NetBeans > >> over > the > >> past releases to enable the vanilla javac from the JDK on which > >> NetBeans runs to be used increasingly better. And ultimately, of > >> course, this > should > >> not be based on the JDK on which NetBeans runs, but on the JDK used > >> by a particular project. > >> > >> Anyway, there have been one or two pull requests around the above, > >> such > as > >> this one: > >> > >> https://github.com/apache/netbeans/pull/2108 > >> > >> A question is what about JDK 8. My bold suggestion would be that we > >> explicitly tell our users that they can’t use our Java Editor if > >> they’re running NetBeans on JDK 8. I’m not saying that we should > >> drop support > for > >> JDK 8. I’m saying we should show a message that the user should > >> switch > to > >> the latest supported JDK for running NetBeans itself on (which of > >> course does not mean that a project can’t use any earlier JDK). > >> > >> Anyway, comments and thoughts welcome. > >> > >> Gj > >> > >> ------------------------------------------------------------------- > >> -- 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 > >> > >> > >> > >> > > --------------------------------------------------------------------- > 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 > > > >
