On 18.10.21 20:31, Neil C Smith wrote:
On Mon, 18 Oct 2021 at 17:44, Michael Bien <[email protected]> wrote:
That's a developer request, right? We don't want to scare regular
NetBeans users with such confusing configuration, I assume. At least
the biggest UX motivation for including nb-javac by default is to
avoid all the download dialogs when one wants to use NetBeans to
develop Java. It should work out of the box.
getting rid of the dialog is a worthy effort i suppose, but is it still
possible to disable the nb-javac module in the plugin manage without
breaking NB after the change?
I'm curious what the difference between a developer request and a user
request really is for us?! I think the average user should expect to
be able to develop against the latest JDK too. Right now, that also
involves not using nb-javac doesn't it? We need a non-scary way to
easily switch nb-javac in and out as people need when their project
setup requires it. And then get rid of the dialog, and download.
also, since automated (!) backporting of javac using jackpot seems to be
feasible now (I don't know how reliable that is)
https://github.com/oracle/nb-javac/pull/12
all what would be needed is to upload weekly builds (pulling from
OpenJDK HEAD) of that module somewhere for those who want to work with
ea JDKs. (and provide a way how to restore the old nb-javac or install
both side by side... etc)
-mbien
Best wishes,
Neil
---------------------------------------------------------------------
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
