Page History

...

• Adopting latest Java language features is simple(r)
• Errors, hints, warnings in the editor match exactly the command line build
• Close co-operation with JDK language team

Cons:

• Distributing GPLv2-CPE licensed component in Apache software is hard - yet possible since

  Jira
  server ASF JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key LEGAL-563

  • it would be way easier to use plain javac  from a JDK

  • nb-javac  has to be downloaded by end-user on demand via autoupdate

• On demand download is problematic

  • user needs internet connection 

  • download server needs to be on (finally nb-javac is at least hosted on Maven central)

  • e.g. sometimes download fails

• Testing matrix is complicated

  • each supported JDK needs to be tested twice - with nb-javac  and without nb-javac 

• Every bug/problem one needs to know whether nb-javac  was or wasn't in use

  • Recent version nb-javac-15  isn't really stable

• nb-javac  is a fork of JDK's javac

  • nobody likes forks

  • ironically Arvind's team is part of JDK organization - e.g. it maintains own fork of JDK's javac 

Status

• Distribution of GPLv2-CPE licensed component approved

  Jira
  server ASF JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key LEGAL-563

• Focus on running NetBeans with javac from latest JDK
  • JDK.next tests - 24 failures as of May 24, 2021

Eliminating the need for nb-javac

...