Community
Participate
Working Groups
There are some files within my project which naturally get out of date compared with Eclipse's view of things - for instance, the vssver.scc file in each directory, left there by SourceSafe. When searching, I never want to include that file - but if I don't refresh the project or directory before searching, Eclipse complains that the project is out of date. Having a simple filter for resources to ignore during searching would make this much simpler.
I'm not familiar with SourceSafe's vssver.scc file(s). If you never want to search those files it would be best to mark those files as derived (either manually by yourself or by the VCM provider) because derived files are excluded automatically. This is the approach we take for files in the (Java builder's) output folders. Another workaround would be to specify the file types in which you want results.
Marking it as derived is a good idea. Unfortunately there's one of these in every single directory - would it be possible to add a filter to say that *all* files matching a certain wildcard or with a certain name are derived? (Not everyone is happy using the VSS plugin, in this case, although I'll ask the plugin maintainer to mark the file as derived - it would certainly make things easier for *me* :) Specifying the file type gets to be a pain when you want to search in lots of different files - if there were an *exclusion* filter in the search dialog that would be easier, and wouldn't require an actual preference, of course. This isn't a biggie, but I don't know how many other people are facing the same kind of thing.
This request will at least have to wait until we can switch to the RegEx support contained in 1.4. We can then introduce a wild card for which stands for "not" in the file pattern entry field.
Fair enough. After a bit of experimentation, it looks possible that using the VSS plugin the file doesn't appear anyway. (SourceSafe is a bit odd in many ways like this.)
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 and remove the stalebug whiteboard tag. 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. --
