Hi Michael,
I've made a test like you have suggested. I've started NB 25 with a new
and empty UserDir and no imported old config and then opened the
Project. Current environment is:
"Product Version: Apache NetBeans IDE 25
Java: 21.0.3; Java HotSpot(TM) 64-Bit Server VM 21.0.3+7-LTS-152
Runtime: Java(TM) SE Runtime Environment 21.0.3+7-LTS-152
System: Windows 10 version 10.0 running on amd64; UTF-8; de_DE (nb)
User directory: E:\test\Netbeans
Cache directory: E:\test\Netbeans\var\cache"
Funny result is: No error badges at all this time. But I've got
errors/exceptions in the messages.log file:
It's flooded with these lines:
"Even though the source level of
C:\Develop\ProjectDir\src\main\java;C:\Develop\ProjectDir\src\main\webapp;C:\Develop\ProjectDir\src\main\resources
is set to: 11, java.util.zip.CRC32C cannot be found on the system module
path: "
Most of the times it's listed like "WARNING [null]: Last record repeated
222 times in total."
I have no clue, what this error is trying to tell me.
And some singleton Exceptions like this:
---------------------------8<-------------------------------------
WARNING [org.netbeans.modules.csl.editor.semantic.SemanticHighlighter]
java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()"
because "highlights" is null
at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.process(SemanticHighlighter.java:167)
at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.processColorings(SemanticHighlighter.java:125)
at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.processColorings(SemanticHighlighter.java:133)
at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.processColorings(SemanticHighlighter.java:133)
at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.lambda$run$0(SemanticHighlighter.java:95)
at
org.netbeans.modules.parsing.api.ParserManager$1.run(ParserManager.java:118)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:197)
at
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:180)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
Caused: org.netbeans.modules.parsing.spi.ParseException
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:186)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:83)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:121)
[catch] at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.run(SemanticHighlighter.java:95)
at
org.netbeans.modules.csl.editor.semantic.SemanticHighlighter.run(SemanticHighlighter.java:57)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:561)
at
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:786)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:288)
at
org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:702)
at
org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:663)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1403)
at
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:287)
at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2018)
---------------------------8<-------------------------------------
Any idea, what is going wrong here? Or any hint what I can do to isolate
the problem more?
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
