| Re: [jdt-ui-dev] Bug to follow the adaption of the new index in JDT UI? |
Adoption of the index in the Open Type dialog is covered here:However, fixing that would require introducing some additional calls to Indexer.waitForIndex to SearchEngine. That poses a deadlock risk unless this is fixed:There's two approaches to fixing bug 509558 (described in the bug). The easiest seems to be a refactoring of the indexer to move the responsibility for gathering artifacts out of the indexer thread and into the thread that requests indexing. That's covered by this bug:I'm working on bug 510212 right now... so that's where we are. :-)- StefanOn Fri, Jan 13, 2017 at 1:43 AM Lars Vogel <lars.vogel@xxxxxxxxxxx> wrote:Hi,______________________________
is there an umbrella bug for JDT UI for the adaption of the new index
in the JDT UI?
I'm particular interested to follow progress in the adaption of the
Open Type History. This is very slow during the first call. Watching
the index creation during the first call of Open Type in our RCP
training sessions is always a source of participant jokes against the
Eclipse IDE.
Best regards, Lars
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com_________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-ui-dev
_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-ui-dev