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.
Decide whether users should need to explicitly save the project file.
We've decided to automatically save the file - except it will be optional. (default=yes)
This sounds good. It gives us an easy way to backpedal if we find out that there is a pressing user need to control project file saving.
Must-have features for milestone3, have impact on APIs (at least potential).
I've replaced the code which used to close, and then open, the project with a new "reopen" call. This is implemented by wiping out the working directory and recreating it from the .project file. Thus, selecting "Reopen" when the .project file has been modified externally now correctly reloads the project. I also added similar code to the Shutdown handler such that if you've turned off auto saving, and you exit with a modified project, answering "No" to the do-you- want-to-save question will cause the changes to be blown away such that the next startup will show the unmodified saved project, not bring you back up in your unsaved state.
done, closing