Whoops .. I forgot to edit the netbeans.conf file to set the path to the
JDK. It was running with a JDK 14-EA build. (I use it for the jpackage
tool)
On Fri, Jan 24, 2020 at 11:23 PM Scott Palmer wrote:
> Made a new Gradle Application and as soon as I was done with the new
> Project dialog a
Made a new Gradle Application and as soon as I was done with the new
Project dialog a popup appeared saying the project couldn't be opened. It
appears to have opened anyway though.
Seeing this exception:
java.lang.NullPointerException
at
Well, the best thing you can do is switching the NetBeans self profiler
on. Do some excessive use of the code completion in several files. Then
switch off the profiler, get the data exported, then attach it to the issue.
I have a machine from 2013 somewhere, I try to dig that up and test as
Working on 11.3b1, probably not an issue.
The "unpacking..." was taking a long time. The system's physical memory
was maxed (win7 with 16 gig ram). So I decided to restart NB and a few
other things. The system is now at half after restarting things. I
expected the indexing to continue when NB
