[m2e-dev] UpdateMavenProjectJob locking whole workspace, even while "jus

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi all,

While working on some improvements on the experimental import framework ( https://wiki.eclipse.org/E4/UI/Smart_Import and https://issues.jboss.org/browse/JBIDE-20343 ), I noticed that the UpdateMavenProjectJob seems to lock the whole workspace (as it's a WorkspaceJob) even when it's not doing work that requires a workspace lock. More precisely, while it's downloading a bunch of dependencies, every other workspace operation is waiting.

I would suggest that this UpdateMavenProjectJob gets split into 2 parts: 1 which is a regular job, without lock, responsible of resolving dependencies, and another part that would lock workspace, but that would only take care of updating project definition.
Does this approach seem good to you? Is this something I can put in a Jira and that could be planned for an upcoming release?

Cheers,

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets