Symbol not found errors during NetBeans indexing on NAS storage
25.5K reputation · 27 Aug 2022, 22:09 UTC
NetBeans utilizes a persistent indexing system to maintain project symbols for code completion and navigation. When project files are hosted on network-attached storage (NAS), the IDE relies on the "Scan for External Changes" mechanism to synchronize the internal index with the disk.
There is an inconsistency in how the IDE detects file system changes on certain network shares, which can result in stale cache entries. This leads to false "symbol not found" errors despite the files being present and updated on the remote server.
While manually deleting the UserDir cache folder forces a full re-index, this is not a viable automated solution for large-scale projects due to the CPU and I/O overhead of the Scan-on-Startup process.
- Does NetBeans provide a configuration to increase the frequency of external change scans specifically for network-mounted directories?
- Is there a documented method to trigger a targeted index refresh for a specific project without purging the entire global cache?