Community
Participate
Working Groups
Build 3.5M3 At some point, a search query may trigger full reindexing indirectly. End user has no clue as to why this is occurring then. Reasons could be: - it had never been indexed before - indexes were corrupted - some classpath change occurred - etc... We should provide an API to surface some explanation that UI could surface (like hover on build progress, or light bulb somewhere...).
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. -- The automated Eclipse Genie.