Hi Michael,

sorry for the late response, I've got hold busy from my customer the last days.

Yes it's a maven Project, some Java EE8 web application (so it's still on the javax Namespace, but the switch to Jakarta is planned in the near future). I'm not sure if there were Exceptions related to the scanning/parsing. I'll have to check this. I'll do some tests when I'm back at work on Monday or Tuesday.

cu
Jens

Am 06.05.2025 um 20:53 schrieb Michael Bien:
On 5/5/25 09:39, Jens Zurawski wrote:
Hi folks,

I have a nasty problem every time I'm updating to a new Netbeans Version, which 
really prevents me from doing it too often. So every now and then I'm skipping 
a version to avoid this issue.

I'm working (besides others) on a big EE application with lots of JSF views and 
composition components and relying on a lot of libs including PrimeFaces, 
OmniFaces, DeltaSpike etc. Now, every time I'm upgrading the Netbeans Version, 
on first opening of this big project, a random number of files (around half of 
them, sometimes more) are marked with the little red error notification icon.
Any exceptions during code scan in the log when this happens?

You can simulate a fresh config by starting NB with --userdir 
"C:\path\to\tempusr1". Once started open the project.

(don't import the config if asked)

what project type are we talking about? maven?

-mbien


And this icon stays there even after a complete Clean and Build cycle (the project builds 
without any error). The only way to get rid of these icons is to open every single file 
into the editor, make some silly change (a single space is enough) and save it again. 
After that the icon eventually vanishes. Once all of the files are "cleaned" 
this way, from that time on Netbeans works like expected and really only marks files with 
errors.

I assume that there is some timing/order conflict in gathering and generating 
all needed informations upon start up and opening a project for the first time, 
but I have no clue, what it could be.

This isn't really a showstopper for me, because in the end everything seems to work, but 
it's annoying and irritating to see lots of "errors" which in fact are not 
errors.
A good workaround for me would be, if I could trigger the 
calculation/generation of these markers once every lib etc. has been scanned 
(or whatever causes that problem) so that I don't have to manually go through 
the whole project and open every second file just to get rid of these icons. Is 
there a way of doing this? Deleting the cache and restarting Netbeans doesn't 
do the trick.

If it matters: This is for Netbeans 25 (but already was this way since older 
versions, but sadly I don't recall when it starts to get my attention), I'm 
using Java 21 on Windows 10

cu
Jens


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to