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.
COS is fantastic, thankyou! If my understanding of the docs is correct -- Compile on Save functionality optimizes compilation so that minimal compiling is done, and done automatically in response to files being changed from within the IDE. The issue with this is that suppose I do a git pull (completely outside netbeans) -- a highly frequent operation, it is unclear whether compile on save actually re-compiles. It doesn't seem to. This means I need to build my project (which, perhaps a separate issue, re-builds dependent projects ad infinitum) before I can run. This means the consequence of pulling minor changes to a handful of files is a 10 minute workspace clean and build. Doing this several times a day in a team setting is somewhat annoying!! Either make it clear in the docs that external changes are not recognized by compile on save. Ideally, please improve "compile on save" to make it actually "compile on change". This is perhaps unrelated -- but is performing a project "build" supposed to rebuild all dependent projects -- this takes ages. Note I'm not using Maven at all. [I'm not moaning -- but (I feel) there are a range of issues with building -- it seems neither Eclipse nor NetBeans can handle building and cleaning nicely -- VS was doing this well in 2008!