This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 271151 - [90cat] NetBeans shows non-existent source problems (due to elder entires in its local configuration))
Summary: [90cat] NetBeans shows non-existent source problems (due to elder entires in ...
Status: REOPENED
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 13:59 UTC by muellermi
Modified: 2017-09-18 11:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (595.12 KB, text/plain)
2017-07-24 13:59 UTC, muellermi 		Details
screenshot (129.72 KB, image/png)
2017-07-24 14:00 UTC, muellermi 		Details
Error "Cannnot find symbol" - but its well known, test runs (159.66 KB, image/png)
2017-07-24 14:07 UTC, muellermi 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description muellermi 2017-07-24 13:59:19 UTC 
Product Version = NetBeans IDE Dev (Build 201707240001)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_141
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.141-b15

Reproducibility: Happens every time

Todays build marks files as errorneous, albeit their is no problem, see screenshot (*after* clean and build)
Using NB 8.2 everything is fine.

I haven't figured out, why these files are marked. As the screenshot shows, no line within the editor is indicated being faulty.
Comment 1 muellermi 2017-07-24 13:59:33 UTC 
Created attachment 164816 [details]
IDE log
Comment 2 muellermi 2017-07-24 14:00:25 UTC 
Created attachment 164817 [details]
screenshot
Comment 3 muellermi 2017-07-24 14:07:46 UTC 
The secons screenshot displays massive error markers within a source file. But this "unknown symbol" is a well known enum and all tests perform well
Comment 4 muellermi 2017-07-24 14:07:52 UTC 
Created attachment 164819 [details]
Error "Cannnot find symbol" - but its well known, test runs
Comment 5 muellermi 2017-07-24 14:14:56 UTC 
Going back to Jaba 8_131, the error markers within the source code disappeared, while the markers on file level still stayed (even after new clean and build)
Comment 6 muellermi 2017-07-24 14:17:08 UTC 
As a last test, I started NB 8.2 with the current Java 8_141 - no such problems
Comment 7 muellermi 2017-08-09 07:36:20 UTC 
Problem still exists in build 20170808
It's a showstopper for testing with productive code
Comment 8 muellermi 2017-09-07 07:50:28 UTC 
With today's build, less classes are shown as error - but there are still lots of them.
The problem occurs especially fornearly all classes of the test packages.
Comment 9 muellermi 2017-09-07 07:55:43 UTC 
When I compile my Maven project using NB 8.2, I'm able to run all tests with NB current build.
But, when I compile the same project using NB current build, then most of the testclasses fail with "uncompilable source code". I'm going to explore, whether different Maven versions are used and if that causes the problem.
Comment 10 muellermi 2017-09-07 08:54:41 UTC 
In both versions (NB 8.2 and Daily Build 20170907), I switched to Maven 3.5.0.
Now both NB versions compile the source correctly. The daily build still shows the errors. Do theses alerts depent on the internal Maven?
Anyway I suggest to bundle Maven 3.5 instead of 3.3.
Comment 11 muellermi 2017-09-18 11:55:49 UTC 
Although this problem changed between certain dev versions, it still existed. After further investigation I discovered that the wrong display had been caused by elder entries within the c:\windows\user\<currentUser>\AppData\Roaming\NetBeans\dev folder or within the c:\windows\user\<currentUser>\AppData\Local\NetBeans\dev folder. Because I deleted both of them, I can not determine which caused the problem. Instead of closing the bug I decreased priority: It seems to be a bug of handling the local configuration. Thus, I added the text wiwithin paranthesis to the summary.