Home » Language IDEs » Java Development Tools (JDT) » Eclipse file search - incomplete result list
|
| Re: Eclipse file search - incomplete result list [message #245329 is a reply to message #245323] |
Fri, 06 July 2007 11:36   |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Agoston,
If there is a reproducible scenario where search fails, you should open
a bugzilla so that it will be fixed. You're sure this isn't simply
being affected by things like choosing to search only in the enclosing
project rather than the whole workspace or by the fact that the regular
expression syntax you are using isn't the one Eclipse is recognizing?
There's a toolbar button on the search view that you can use to rerun
the search (F5), but I suppose you are saying this just fails to really
do a search, in which case, it should be easy to create a reproducible
bug report...
Agoston Bejo wrote:
> Hi!
>
> I have been wondering for a while now why Eclipse's search
> functionality is so unreliable. Very often (in about 25% of the cases)
> Eclipse simply doesn't find all the matches. If I want to be sure
> about the results, I always have to use some other tool to search for
> the pattern in the files of the project.
>
> a) Is there a remedy for this behavior?
>
> b) The results of the searches are cached, therefore even if I refresh
> my project and search for the same pattern again, the search is not
> re-run, only the cached (false) result is shown immediately. Is there
> a way to force Eclipse to perform the search again for real?
>
>
> Thank you,
> Agoston
>
|
|
|
| Re: Eclipse file search - incomplete result list [message #245339 is a reply to message #245329] |
Fri, 06 July 2007 12:42 |
 Agoston Bejo
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hi Ed,
another interesting fact (this might be a clue): if I open a file that
contains the pattern but was not included in the search results (a missed
hit), then re-run the search, it will find that as well from then on (but
not the rest of the missed ones). It's as if it is some caching or
indexing problem...
See also below!
Ed Merks wrote:
> Agoston,
> If there is a reproducible scenario where search fails, you should open
Unfortunately it's *NOT REPRODUCIBLE*. It's a relatively huge project
we're working on (2000+ java files), and it only happens from time to time
undeterministically (as far as I'm concerned). The only deterministic
thing is once a specific search combination gives incorrect results, it
will return that same result the next time, too. (I have tried out
refreshing the results with F5, and it does re-execute the search - but
the result is the same incorrect one.)
> a bugzilla so that it will be fixed. You're sure this isn't simply
> being affected by things like choosing to search only in the enclosing
> project rather than the whole workspace or by the fact that the regular
> expression syntax you are using isn't the one Eclipse is recognizing?
*NO REGEX* included. Yes, usually I define a *WORKING SET* to search in,
but it does contain those files. However, I just tried it out setting the
scope to 'Workspace' - still only the reduced result set. (I have a case
right in front of me, so I'm able to experiment with the phenomenon.)
> There's a toolbar button on the search view that you can use to rerun
> the search (F5), but I suppose you are saying this just fails to really
> do a search, in which case, it should be easy to create a reproducible
> bug report...
No, this is not the case. (See above.) F5 works correctly, the search
itself doesn't, and it's not reproducible.
Thanks,
Agoston
> Agoston Bejo wrote:
>> Hi!
>>
>> I have been wondering for a while now why Eclipse's search
>> functionality is so unreliable. Very often (in about 25% of the cases)
>> Eclipse simply doesn't find all the matches. If I want to be sure
>> about the results, I always have to use some other tool to search for
>> the pattern in the files of the project.
>>
>> a) Is there a remedy for this behavior?
>>
>> b) The results of the searches are cached, therefore even if I refresh
>> my project and search for the same pattern again, the search is not
>> re-run, only the cached (false) result is shown immediately. Is there
>> a way to force Eclipse to perform the search again for real?
>>
>>
>> Thank you,
>> Agoston
>>
|
|
|
| Re: Eclipse file search - incomplete result list [message #245346 is a reply to message #245339] |
Fri, 06 July 2007 12:58 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Agoston,
I wonder if there might be clues in the Error Log that something is
failing? (I hate those hard to reproduce bugs both as a user and as a
developer wanting to fix them.)
Agoston Bejo wrote:
> Hi Ed,
>
> another interesting fact (this might be a clue): if I open a file that
> contains the pattern but was not included in the search results (a
> missed hit), then re-run the search, it will find that as well from
> then on (but not the rest of the missed ones). It's as if it is some
> caching or indexing problem...
>
> See also below!
>
> Ed Merks wrote:
>
>> Agoston,
>
>> If there is a reproducible scenario where search fails, you should open
>
> Unfortunately it's *NOT REPRODUCIBLE*. It's a relatively huge project
> we're working on (2000+ java files), and it only happens from time to
> time undeterministically (as far as I'm concerned). The only
> deterministic thing is once a specific search combination gives
> incorrect results, it will return that same result the next time, too.
> (I have tried out refreshing the results with F5, and it does
> re-execute the search - but the result is the same incorrect one.)
>
>
>> a bugzilla so that it will be fixed. You're sure this isn't simply
>> being affected by things like choosing to search only in the
>> enclosing project rather than the whole workspace or by the fact that
>> the regular expression syntax you are using isn't the one Eclipse is
>> recognizing?
>
> *NO REGEX* included. Yes, usually I define a *WORKING SET* to search
> in, but it does contain those files. However, I just tried it out
> setting the scope to 'Workspace' - still only the reduced result set.
> (I have a case right in front of me, so I'm able to experiment with
> the phenomenon.)
>> There's a toolbar button on the search view that you can use to rerun
>> the search (F5), but I suppose you are saying this just fails to
>> really do a search, in which case, it should be easy to create a
>> reproducible bug report...
>
> No, this is not the case. (See above.) F5 works correctly, the search
> itself doesn't, and it's not reproducible.
>
> Thanks,
> Agoston
>
>> Agoston Bejo wrote:
>>> Hi!
>>>
>>> I have been wondering for a while now why Eclipse's search
>>> functionality is so unreliable. Very often (in about 25% of the
>>> cases) Eclipse simply doesn't find all the matches. If I want to be
>>> sure about the results, I always have to use some other tool to
>>> search for the pattern in the files of the project.
>>>
>>> a) Is there a remedy for this behavior?
>>>
>>> b) The results of the searches are cached, therefore even if I
>>> refresh my project and search for the same pattern again, the search
>>> is not re-run, only the cached (false) result is shown immediately.
>>> Is there a way to force Eclipse to perform the search again for real?
>>>
>>>
>>> Thank you,
>>> Agoston
>>>
>
>
|
|
|
| Re: Eclipse file search - incomplete result list [message #245356 is a reply to message #245339] |
Fri, 06 July 2007 19:38 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Agoston Bejo wrote:
> Hi Ed,
>
> another interesting fact (this might be a clue): if I open a file that
> contains the pattern but was not included in the search results (a
> missed hit), then re-run the search, it will find that as well from then
> on (but not the rest of the missed ones). It's as if it is some caching
> or indexing problem...
I'm pretty sure there is no internal caching of search results.
Based on what you've said, my first suspicion is that you have files
that are being modified outside of Eclipse. If so, you need to make sure
to refresh the containing Project(s) in Eclipse in order for the
external changes to be detected. Eclipse does not, by default, monitor
for arbitrary changes to the file system, so it is possible some other
process has touched the files and Eclipse doesn't know about it yet.
Is that the case in your situation?
Eric
|
|
|
Goto Forum:
Current Time: Sat Nov 09 04:56:39 GMT 2024
Powered by FUDForum. Page generated in 0.03585 seconds |
] 
Search
Help
Register
Login
Home
