Summary: | [Search][File] Need option to search only shared files (i.e. stored in SVN, git, etc) | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Yegor Jbanov <yegor.jbanov> |
Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | daniel_megert, markus.kell.r, remy.suen, tomasz.zarna |
Version: | 3.6.1 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Yegor Jbanov
2010-12-03 12:57:39 EST
Sounds reasonable, but isn't it more an enhancement request for Platform/Search? I can imagine a new checkbox in TextSearchPage that would make the search confirm with Team.isIgnoredHint(IResource)[1] whether a resource should be included in the scope. [1] note that Team.isIgnoredHint(IResource) first checks if a given resource is derived (In reply to comment #1) > Sounds reasonable, but isn't it more an enhancement request for > Platform/Search? I can imagine a new checkbox in TextSearchPage that would make > the search confirm with Team.isIgnoredHint(IResource)[1] whether a resource > should be included in the scope. The problem is that Search does not depend on Platform Team (and that should no change). Platform Resources already has some Team related knowledge (org.eclipse.core.resources.IResource.TEAM_PRIVATE). If it would also know about ignored resources then Search could do what you suggest. See also bug 244968 and bug 37534. Yegor, a workaround could be to mark the files as derived and then make sure the checkbox is cleared on the File Search tab. Thanks, Markus. I'll take a look at the "Derived" option. I never realized it was there. I agree that Search should not have a dependency on Team. However, it would still work if the dependency went the other way - if Team had a dependency on Search. Search could allow third-party plugins register custom search filters. Team would then install a Search filter for ignoring certain files based on Team properties. (In reply to comment #4) > Thanks, Markus. I'll take a look at the "Derived" option. I never realized it > was there. > > I agree that Search should not have a dependency on Team. However, it would > still work if the dependency went the other way - if Team had a dependency on > Search. Search could allow third-party plugins register custom search filters. > Team would then install a Search filter for ignoring certain files based on > Team properties. Sure, but in this case it might be easier to just add the ignored team resources knowledge to the Resources plug-in. 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. |