Community
Participate
Working Groups
Build ID: I20061214-1445 Steps To Reproduce: 1. Share Project with subclipse (svn) 2. ctrl-shift-r 3. search something More information: If i use the new Open Resource Dialog with working sets, the search result always contains the files from the .svn subdirectories. So if your are searching for Foo.java, you'll find also Foo.java.svn-base file. It would be nice to have an exclusion set in working sets
We would be interested in seeing any suggested patch
The files from the CVS directories don't show up because the CVS plug-in marks them as team-private. It sounds like the Subclipse plug-in does not do this but instead relies on the .*Resource filter to hide the .svn directory. If the Subsclipse plug-in marked the .svn directory as team-private, the .svn directory and it's contents would not appear.
Subclipse marks resources as team private. Always has. There are a number of problems you get if you do not do this, such as the resources being copied to the build output folders.
OK, I think I missed an important part of the steps. This happens when sharing a project. I suspect what is happening is that the meta files are being created and noticed by the Find Resource dialog before they get marked team-private. I can't really try this since I don't have write access to an SVN repository but we've had similar problems with CVS. To address the CVS problem, we added API in 3.2 to mark a resource team0provate when it is created (see bug 50965). However, this isn't always possible since the files may be created by a non-Eclipse aware library. Stefan, you can verify whether this is the problem by restarting Eclipse and trying the Find again. If the SVN files no longer appear, this would indicate whether I am correct in my assessment.
Krzysztof left the team some time ago. I'm removing the target milestone.
Reassigning to Susan.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.
