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.
The project settings are versioned by versioning the project file. In the UI, updating, adding and committing to VCS must always distinguish between the source data and the project file (presented as project settings). In other words, the user must be able to handle them separately -- e.g. through different commands in menus. But there must be also a clear default way to manipulate the whole project consistently to avoid problems with different versions of the project settings and project contents.
Reassigning vcscore issues to versioncontrol->vcscore.
I would like an option for the project where the user can choose if the project settings are versioned or not. I started a project at SourceForge.net and I think that users who might want to participate do not need the project settings of netbeans, if they do not use it. So I want the option that only the source files (or maybe the testfiles, too) are versioned. The implementation could be like this: the user right-clicks on a folder->subversion-> and here he could coose "include this folder" or "exclude this folder". If he would right-click the project folder, it could look like folder->subversion-> "include project with project settings" and "include project without project settings". Or / and these functionality should be avaible during the commit-process. But it would be really useful.