Community
Participate
Working Groups
Please make it possible to exclude any user-specified resource from version control, or at least to keep it from appearing in the Synchronize view. CVS flaws do not really matter (see other related bugs for a lengthy discussion of issues involved). Not being able to simply and reliably filter out resources from the "Synchronize" view without fiddling with the CVS server is a serious usability flaw.
I agree that this would be handy. We will try to do it for 3.1, if time permits.
*** Bug 80027 has been marked as a duplicate of this bug. ***
*** Bug 110261 has been marked as a duplicate of this bug. ***
*** Bug 112758 has been marked as a duplicate of this bug. ***
*** Bug 135340 has been marked as a duplicate of this bug. ***
*** Bug 169710 has been marked as a duplicate of this bug. ***
*** Bug 171008 has been marked as a duplicate of this bug. ***
Most dups refer to directories that were created, but I have another use case. The practice within our team is to commit the Eclipse .project file to CVS. We all use Maven and the Maven plug-in, so this allow team members to check out a project and the Maven nature is already added to the project. However, individuals may install additional plug-ins that are not common to everyone, and this modifies the .project file with new natures, <buildSpec> elements, etc. We do *not* want to commit those changes because they are not universally used across the team. However, it is easy to accidentally check in .project file changes because the Synchronize with Repository view includes .project even if we add it to .cvsignore. On large commits, its easy to miss it. Then, others get them on CVS updates, and then they get workspace errors about missing pieces. So, I'd like a way to tell Eclipse to *really* ignore files that are listed in .cvsignore - it would be an option in the CVS preferences, but off by default. Simply automatically "remove from view" anything that is in a .cvsignore file.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.