Hello Geertjan and others,
Unfortunately also with NB 11.3 alpha, the same Null pointer exception occurs
frequently at compile time, with non-installed nb-java plugin.
But I observed the following:
While the null pointer exception in its stack-trace lists this (which you
quoted earlier) :
-> at org.netbeans.lib.nbjavac.services.NBAttr.visitClassDef(NBAttr.java:66)
… and the nb-javac plugin isn't installed (which for many, including me,
would be located in the user's home, here under Linux it's: .netbeans/11.2/
), there's still a hard-wired module inside the netbeans application folder,
this:
-> netbeans/java/modules/org-netbeans-lib-nbjavac.jar
This jar file stays there, even if nb-javac plugin isn't installed (or
un-installed) in the user's home.
Could this be the problem?
For now, the situation for my mid-sized OpenJDK 11 project is as follows:
a) With installed nb-javac plugin:
No null-pointer exceptions at compile time, but refactoring-rename doesn't work.
b) Without the nb-javac plugin:
Frequent null-pointer exceptions at compile time, however refactoring-rename
works fine.
Strange. The null pointer exception doesn't block anything, it seems, i.e. I
can continue to work with the project in NB. But since the exception is shown
in red an occurs frequently when compiling, it's irritating. Also I am at my
wits' end. :-)
Greetings,
Hans
Am 25.02.20 um 15:41 schrieb Geertjan Wielenga:
Definitely try 11.3.
And possibly nb-javac is disabled, though still installed.
Gj
On Tue, Feb 25, 2020 at 3:39 PM Hans Grimmelshausen HG <far...@mail.de
<mailto:far...@mail.de>> wrote:
Hello Geertjan and other readers,
Your observation makes sense, but the strange thing is that I did
uninstall nb-javac via NB's menu Tools->Plugins. So it's shown under
"Available Plugins".
Also I can successfully refactore-rename methods etc in my mid-sized
project, which hasn't been working with an installed nb-javac. Like
Thomas suggested, disabling nb-javac wasn't enough, it had to be
un-installed.
I even tried with a fresh NB profile, but the null pointer exceptions
keep up coming.
This is all very strange to me. Since indeed the nb-javac mention is in
the stacktrace.
Maybe I should try NB 11.3 ?
Thanks.
Greetings,
Hans
Am 25.02.20 um 11:52 schrieb Geertjan Wielenga:
Since this is in the stacktrace, nb-javac must still be present, i.e.,
has not been uninstalled:
at
org.netbeans.lib.nbjavac.services.NBAttr.visitClassDef(NBAttr.java:66)
Gj
On Tue, Feb 25, 2020 at 11:48 AM Neil C Smith <neilcsm...@apache.org
<mailto:neilcsm...@apache.org>> wrote:
On Tue, 25 Feb 2020 at 10:35, Hans Grimmelshausen (HG)
<far...@mail.de <mailto:far...@mail.de>> wrote:
> Geertjan wrote at
> one point that the nb-javac plugin was mainly useful for JDK 8
projects.
Mainly useful for running NetBeans itself on JDK 8 as far as I know.
And for supporting versions of JDK above what the IDE is running on.
Maybe it's time to take the plunge and stop supporting NetBeans on JDK
8 from 12.1?!
Best wishes,
Neil
--
Via Netbeans-Apache
