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.
Summary: | [90cat] NetBeans shows non-existent source problems (due to elder entires in its local configuration)) | ||
---|---|---|---|
Product: | ide | Reporter: | muellermi <muellermi> |
Component: | Code | Assignee: | issues@ide <issues> |
Status: | REOPENED --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.1 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
IDE log
screenshot Error "Cannnot find symbol" - but its well known, test runs |
Description
muellermi
2017-07-24 13:59:19 UTC
Created attachment 164816 [details]
IDE log
Created attachment 164817 [details]
screenshot
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 Created attachment 164819 [details]
Error "Cannnot find symbol" - but its well known, test runs
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) As a last test, I started NB 8.2 with the current Java 8_141 - no such problems Problem still exists in build 20170808 It's a showstopper for testing with productive code 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. 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. 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. 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. |