This one is interesting (NB 11.3 Win 10). The navigator breaks on the
code below, but only under a very strange set of conditions that appear
to be related to the alternate use of ${service} rather than {$service}
in the throw message.
Sometimes the navigation window works, but if I change
Hi
I tried this, I thought it had worked but it didn't. I still have a couple
of classes that have this issue (it fixed a lot though).
The errors are all to do with return types (thinking they are object) or
incorrectly saying a method doesn't exist on a class
Peter
On Sun, 5 Apr 2020, 14:46
I'm encountering this too at times. I think it's a caching issue.
This works for me:
Go to the NetBeans cache directory, which is platform specific. On Linux
it's in .cache/netbeans/VERSION
Clear everything but not mavenindex and mavencachedirs. I'm sure that not
all files and folder must be
Hi
Netbeans seems to cache compile errors and on startup immediate flags those
compile errors with a red underline and red marker.
I am assuming to be the case if it's wrong then the question will have to
change slightly.
I am getting incorrect compile errors highlighted in red which persist
Hi Mike,
Tested yesterday on a Windows box, and was able to download/unpack
Payara 5.194 via the NetBeans UI. I think combined with the 504
error, this would suggest a temporary blip at the remote end.
Thanks for flagging this!
Cheers,
P
On Sat, Apr 4, 2020 at 2:01 PM Mike Ryan wrote:
>
>
