I have experienced this as well. The best that I have been able to do is
rely on build output. Don't know if anyone else is looking into this
problem. It gets tedious when this happens for a complex build. It seems to
happen for me most often when there is a problem with generic parameters.
I have had this problem for years, but closing and reopening solves it.
I've always thought it's a memory exhaustion problem (despite having a
lot of memory).
Tilman
On 12.06.2024 22:49, Mitch Claborn wrote:
This happens to me occasionally, usually when editing a fairly large
java file. The
This happens to me occasionally, usually when editing a fairly large
java file. The icon in the tab will show a red indicator for a compile
error, but there are no red indicators on the right gutter to show which
lines have the error(s). If I'm lucky enough to find one the errors on
my own,
The best would be to use the Gradle Java Toolchain feature.
https://docs.gradle.org/current/userguide/toolchains.html
That's a bit other way around, Gradle may download and install a JDK
with the specified version if that version does not exist in your system.
NetBeans 22 is going to respect
