|Re: [cdt-dev] CDT ignores IWorkspace.AVOID_UPDATE|
Thanks for the answer.
I made a bugzilla that basically says the same as I said here on the list and a gerrit that contains a unit test that demonstrated the perceived problem.
The gerrit contains 3 tests. Now 2 fail. If it is changed to the way I think is should work all 3 test should be successful.
I only have vague recollection of debugging this sort of issue, like https://bugs.eclipse.org/bugs/show_bug.cgi?id=375226It might help to create a bugzilla and post some stack traces to illustrate what is going on.If I remember correctly, calling setProjectDescription starts a workspace runnable with a workspace scheduling-rule/lock (by default) and it fires an APPLIED event at the end which triggers a indexing job. But I don’t know where the resource event fits in your case.
On Oct 1, 2020, at 8:50 PM, Jan Baeyens <jan@xxxxxxxxxx> wrote:
I'm still trying to find a way to make to postpone the indexer untill "it is safe" during cdt project creation.
When doing so I noticed that ICProjectDescriptionListener events are triggered when running a thread started with the IWorkspace.AVOID_UPDATE flag
As to the documentation I would assume the ICProjectDescriptionListener events to be non-existing in regards to changes done by the AVOID_UPDATE invoked thread.
Am I understanding this correctly? Should I create a bugzilla?
flag constant (bit mask value 1) indicating that resource change notifications should be avoided during the invocation of a compound resource changing operation.
cdt-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
Back to the top