Updating Maven dependencies for Eclipse plug-ins blocks the workspace

[vogella]

In the past I did not install M2e into the Eclipse instance I used for Eclipse plug-in development. Now with the great Maven integration for libraries in the target platform initiallly created by @laeubi I "have to".

It seems that Maven dependency update blocks the whole workspace. See screenshot. Can this be less blocking? If think @mickaelistria implemented some rules for only blocking the affected project. Why is M2e updating my plug-in dependencies anyway? Is M2e not delegating to PDE for plug-ins?

[laeubi]

@vogella have you imported the projects as maven projects or as eclipse projects? If they are "pure" eclipse project m2e should not do any harm otherwise you are maybe affected by

• M2Eclipse gets stuck in endless update loop #123
• Loop between "Building" and "Downloading Sources and Javadoc" #252

[vogella]

@laeubi AFAICS org.eclispe.ant.test.ui has no reference to Maven. I imported them as Eclipse projects before install m2e.

[laeubi]

org.eclispe.ant.test.ui has no reference to Maven

If I understand the screenshot correctly the org.eclipse.equinox.launcher project is actually updated (and blocking the refresh of the ant one...)

Would it be possible to create some Threaddumps and attach them here? Or could this be reproduced using public sources / reproducer project?

[Madjosz]

Here I have the same problem that "Updating Maven Project" blocks the complete workspace making Eclipse effectively unusable. I can type one character and then "User operation is Waiting" comes up and I need to wait for all of my projects to recursively build my whole project tree again and again until the typed character appears after after 10 minutes. Reminds me of the good old "You moved the mouse. Please restart the computer for the changes to take effect." /rant

I made a thread dump while waiting. Maybe it can be of any help.

threaddump.log