Supporting multiple releases of javac (from different JDKs) complicates NetBeans code.
download server needs to be on (finally nb-javac is at least hosted on Maven central).On demand download (of newest javac on old JDKs) is problematic Close co-operation with JDK language team.Errors, hints, warnings in the editor match exactly the command line build.Adopting latest Java language features is simple(r).Relying on Javac has some positive aspects, but also some downsides. PR-2783 allows compilation against JDK-17 Javac API - removes need for (reflection & co.) hacks.PR-3251 includes the here-in proposed Javac in all NetBeans complementary binaries.PR-1 makes sure only Classpath exception covered files are used in the nb-javac generated binary.
PR-3206 integrates the below proposed solution into NetBeans 13.Repository with automatically generated nb-javac.Historically NetBeans project relies on nb-javac for Java editing features, i.e., parsing and lexing, for features such as syntax coloring, code completion, refactorings, and the like.