Bug 110479

Summary:	[index] Java indexing job should not be system task
Product:	[Eclipse Project] JDT	Reporter:	Eugene Kuleshov <ekuleshov>
Component:	Core	Assignee:	Frederic Fusier <frederic_fusier>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	P3	CC:	kent_johnson
Version:	3.1
Target Milestone:	3.3 RC4
Hardware:	All
OS:	All
Whiteboard:

Description Eugene Kuleshov

2005-09-23 14:23:14 EDT

When Java indexin job is running the whole workbench is less responsible and in
some cases it may cause some memory issues (on complete reindex) that could be
difficult to track down. However you can only see its progress by enaling
showing system jobs in a process view.

Please make this job to appear on default process view configuaration to make it
more verbose to the user.

Comment 1 Robert L. Snyder

2006-01-19 14:46:12 EST

Another reason to do this:  Java indexing is started when the project is opened - reasonable.  However, for large projects it can go on for a long time.  The user may well know that no java files have changed since the last time (or may not care that they have).  Fortunately you can just stop the process, but you have to have all of the other system tasks visible to do so.

Comment 2 Frederic Fusier

2007-06-19 15:40:55 EDT

I do not think this must be changed. If user has an easy access to this job, he/she may cancel it and then after complain that his/her search requests do not work!

Only advanced user should be able to cancel this job and so we'll keep it as system one.

Comment 3 Frederic Fusier

2007-06-19 15:41:57 EDT

(In reply to comment #1)
> Another reason to do this:  Java indexing is started when the project is opened
> - reasonable.  However, for large projects it can go on for a long time.  The
> user may well know that no java files have changed since the last time (or may
> not care that they have).  Fortunately you can just stop the process, but you
> have to have all of the other system tasks visible to do so.
> 
As indexing store the results in files, only changed/added files are re-indexed. So, no specific indexing should occur at the startup. If you notice unexpected indexing during the startup sequence, then please open a specific bug.