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.
1. Create a new file in a versioned directory 2. Exclude it from commit using the action in the CVS menu (BTW, we could get into a discussion about the "Exclude from commit" concept as such, but that would be a long debate) => There is no visual indication that this file will be excluded, the icon and the color are the same as for other new files which have not been excluded. This makes it very easy to make a mistake during commit. Compare this to e.g. WinCVS, which distinguishes between local files, files that were "cvs add"-ed and files that were "cvs remove"-d. Also, because (as I understand) that these files are excluded from diffs, the lack of visual distinction also makes it very difficult to debug problems such as "why does this file not appear in the diff? I know it's modified". Compare to command line diff, where *all* modified files appear in some way (? or A or R or M). Keep the user in control, please. This is a major usability problem.
In the original spec, the Exclude from Commit action was only available from the Versioning (CVS) view and in this view excluded fies are striked through. We can strike through also files in all other places (Projects, Files, editor tab, etc.) , but this is a question for HIE (ccing). Excluded files are not present in Diffs so that they do not clutter the view ... in most cases you are diffing before commit and having excluded files there is counter-productive. You can diff them though but you have to select them for Diff explicitly. All in all, current spec seems OK to me .... HIE, any opinions?
Hi, the Versioning (CVS) window shows excluded files from commit. We have indication of excluded files. This information is necessary to have. But it is not suitable to show striked files in project window. The current solution covers most cases. The spec is OK from my point of view. Josef