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.
When the whole project is in under CVS, the new/copied/moved files are automatically added into CVS as well (cvs add command is executed). It is not possible to turn off this default behavior. Usually I want to have full control over what goes into CVS and what doesn't. Thus a switch that would allow to turn of this default behavior is really a need-to-have for anybody who wants foll control over his/her repository. Automatic exclusion from commit in the Options dialog does not solve the issue, as it makes CMD line cvs command execution problematic. Better coloring scheme for CVS file status would help as well. In IntelliJ Idea, the files that are not (yet) versioned are displayed as brown so they are easy to distinguish from others.
Created attachment 54069 [details] Zipped GlassFish logs
Created attachment 54070 [details] Gzipped messages.log
Sorry, the attachments belong to the issue #123486. It's just the idiotic CollabNet behavior that automatically advances to the next issue in the query list once you commit changes in the current issue...
This was our design decision. Exclude From Commit status is an inverse operation to Add. We have found that Adding files manually is just an annoying misfeature for most CVS users. As you noted, we now have an option to automatically Exclude new files from commit and if you want you can change that in the IDE. You can also Add files from command line if you want to. Best way to avoid thinking about what to add and what to keep private is having a separate dir for private files. See also http://wiki.netbeans.info/wiki/view/FaqSubversionExludeByDefault *** This issue has been marked as a duplicate of 89805 ***
I am sorry but I have to question the design decision. To me there are more than 2 states of the file WRT versioning: 1. versioned 2. not versioned (yet) 3. excluded from versioning (i.e. "ignored" in CVS) Current design simply omits the state 2. I cannot comment on what group of CVS users (students vs. professional developers) you used in your usability testing as I don't have enough information about those tests. Still as a professional developer I would prefer having a full control and overview over what is the current state in versioning and what happens when I create/add/copy/delete a file in a project and what does not. There are simply situations during the development, where one doesn't want to version some files YET. It does not however mean that the files are not intended for versioning at all. The idea of having separate dirs for private files thus does not address the problem discussed here. Also, I am reopening the issue because the incomplete coloring scheme for versioned files is not addressed in issue #89805 . The problem is related to the missing file state described above. Currently there is following scheme mapped to the versioning state of a file: 1. file/dir not under version control : MISSING 2. file/dir versioned, locally unmodified : black 3. file/dir versioned, locally modified : blue 4. file/dir newly added for versioning: green 5. file/dir explicitly excluded (ignored) from versioning: gray 6. file/dir versioned, scheduled for removal: no color, file is missing => "restore" operation is problematic Note 1: Actually, in version controlled directories files in state 1. are displayed as green, same as files newly added for versioning, which adds to overall confusion. Note 2: IntelliJ Idea has an elegant (= intuitive, user-friendly) solution available for the things we are talking about here for several years already...
Your request is that we distinguish Added files vs. New files yet you do not distinguish Removed and Deleted files. And THIS is not intuitive as you can see. We just took the approach that we have ONE state for New/Added files and one state for Removed/Deleted files. Historically, CVS has two states for both and we decided that this redundancy is neither intuitive nor practical for normal use. So, let me correct the table: 1. file/dir not under version control : green 6. file/dir versioned, scheduled for removal: no file => no color, removed files are visible is the Versioning/CVS view 7. file/dir versioned, deleted from disk: no file => no color, deletde files are visible is the Versioning/CVS view Let us continue this discussion in Issue #89805 if you please, it is counterproductive to have 2 records open for one issue. --------------------- So I will change summary of this issue to cover the coloring scheme. We do not have a nice GUI for changing coloring but still you can customize it using command-line options, see http://wiki.netbeans.info/wiki/view/FaqSubversionColoring (just replace "svn" with "cvs") As for IDEA, it just follows what CVS has to offer - different coloring (state) for Unversioned and Added files and you have to manually add files to CVS.
The issue #89805 is marked as resolved. Do you really want to continue our discussion there? Btw., from your post: "As for IDEA, it just follows what CVS has to offer - different coloring (state) for Unversioned and Added files and you have to manually add files to CVS." - That's exactly what I would expect from a professional IDE - full control over what I am doing. The user-friendliness is always a welcome bonus: nice feature about IntelliJ Idea is that when you are adding/moving a file, you have an option in the confirmation dialog that let's you control whether or not the newly added file will be versioned or not.
Yes, please continue there and feel free to reopen it with your justification if you wish.
Closing the issue to continue the discussion on a reopened issue #89805. *** This issue has been marked as a duplicate of 89805 ***