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.
Product Version = NetBeans IDE Dev (Build 20150126-1d18233786f7) Operating System = Linux version 3.16.0-29-generic running on amd64 Java; VM; Vendor = 1.8.0_25 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.25-b02 NB has an API IndexingBridge which is supposed to prevent classpath scanning from being initiated in response to filesystem changes while a (Maven, e.g.) build was in progress inside the IDE, at least unless the build paused for a long time with no output (IIRC 10+s). This no longer seems to work. I “Clean and Build Project” and see classpath scanning start up and finish a couple times in the middle, even during a quick and active build, probably in response to source generation. The result is that I get bogus IDE-compiled classes with various bytecode errors stuck in target/classes/ and breaking tests, even though I did a clean build specifically to obliterate them and replace them with standard javac output. Regardless of correctness issues in the classpath scanner, the excessive scanning also slows down the system, and thus the build. The only workaround I can see is to close the project and do the clean build from a shell.
could not reproduce for a simple project. when running with -J-Dorg.netbeans.modules.project.indexingbridge.IndexingBridge.level=FINE maven seems to set the protected mode on and off as expected. is this still the case? if yes, please provide a sample project,
Hopefully fixed. jet-main http://hg.netbeans.org/main-silver/rev/84d2ef958514 Jesse, if you can reproduce it with the above fix please reopen. I was not able to reproduce it. Thanks a lot.