I haven’t seen anything interesting in the log file yet. Note: In my current NB process auto-complete for “java.net <http://java.net/>.” works as expected, but not “java.” or “java.n”
Auto-complete for “Collect” will not suggest “java.util.Collections”, but “java.util.” will. Basically if it has to complete a package name in java.* it will fail. If I type a complete package name, completing classes (but not packages) will work. So java.util. will not suggest java.util.stream package, but it will suggest all classes in java.util. Typing java.util.stream. will suggest classes in that package. Note that there is no delay before it claims it has no suggestions. So taking a profiler snapshot isn’t practical. (Ha! - NB on Windows is fast when it isn’t working :-) ) Scott > On Sep 10, 2019, at 12:17 PM, Geertjan Wielenga <geert...@apache.org> wrote: > > When it happens, look in the log file to see if there are relevant error > messages. > > Gj > > On Tue, 10 Sep 2019 at 18:06, Scott Palmer <swpal...@gmail.com> wrote: > >> I have found on multiple occasions that NetBeans “loses its mind” and >> forgets items on the classpath. >> >> I use exclusively Gradle projects. >> >> I have found that after working for a day and coming back in to the >> office (work computer is left on in case I decide to work remotely), >> sometimes the open projects complain about not finding classes that are >> clearly there. >> >> This morning I attempted to edit a source file and NetBeans is failing to >> autocomplete anything in the java. package. >> >> I type: >> >> java. >> >> and the popup says “No suggestions”. Really? You forgot all of the core >> Java packages?? >> >> If I type: >> >> Ma >> >> and invoke auto-complete it will suggest to me Math from java.lang, or >> “Str” will suggest ’String" so it is aware of classes in that package. But >> even typing “ja” and invoking auto-complete automatically completed >> “javax.” as if “java.” wasn’t an option >> >> I’ve even had NetBeans fail to auto-complete names of basic classes like >> String though. >> >> >> Restarting NetBeans will fix the problem. The projects in question always >> build correctly from the command line. >> >> >> I’m not sure what to write in a bug report, this happens for all Gradle >> projects as far as I’m aware. I don’t know what triggers it other than >> time. I.e. eventually it happens on projects that were working fine when I >> started NB. >> >> Regards, >> >> Scott
