commit 8d90fb030df310a974aae5d27d0bc2610c1a14ad
author Mikael Barbero <mikael@eclipse.org> Fri Sep 23 14:37:09 2016 +0200
committer Sergey Prigogin <eclipse.sprigogin@gmail.com> Fri Oct 07 14:37:36 2016 -0400
tree a304358cc05e133e1a095d19eecb481fb541214d
parent e3ca55c89126d0ea240aed2fdcd1172b4f16ae75

Bug 501997 - Initialize the workspace in a background job

Workspace initialization activates some extensions in a synchronous way
(like IRefreshProvider). The activation of these extensions can take a
long time, so it's better to initialize the full workspace in a
background job.

Note that it does not help the Eclipse workbench to start faster because
EMF asks for ResourcesPlugin#getWorkspace() very early. It blocks until
the workspace is fully initialized, but this does not happen during
bundles initialization.

Change-Id: Ie0b324945315094e9835d367a87016d69f09b8e4
Signed-off-by: Mikael Barbero <mikael@eclipse.org>