Hi Ty,
NetBeans 13 will be the first release where nb-javac 17 its enabled by
default. This simplified a lot since NB does no longer have to deal with
javac versions <17.
nb-javac is basically no longer optional unless you run on 17+ and know
what you are doing (advanced user who is ok of running outside the
supported range of JDKs).
I agree that there should be a warning dialog at the very least to
notify the user if a particular config (e.g running on JDK 18+) is not
supported and maybe explain the options from there. Contributions
welcome, would be great to add this to NB 14.
for experiments:
- start NB on a supported JDK at least once and make sure the java
cluster has loaded
- start on JDK 18+ only if you have nb-javac already uninstalled
- good luck!
-mbien
On 02.02.22 20:16, Ty Young wrote:
(Sorry for the previous email)
Hi,
After firing Netbeans 13 up on an in-dev JDK build I was immediately
hit with errors due to nb-javac and Java 19. It would have been nice
if I was prompted first as a user as to whether I wanted to use it.
Removing nb-javac caused more havoc. Upon restart, Netbeans closed any
project that wasn't a parent Maven project, didn't let me open or
right click any project, and the notifications table was white(not
respecting L&F like rest of IDE).
Strangely, exiting the IDE, switching to a slightly older JDK 18
build, and relaunching seems to have fixed all of the issues. Even
*after* switching back to 19.
---------------------------------------------------------------------
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
