spring-tools: STS stuck on Updating Maven Project - Resolving Plugin Dependency 75%

Using STS 4.17.0 - JDK 17.0.2 - Windows 10 I often have eclipse stuck on Updating Maven Project - Resolving Plugin Dependency 75%. The GUI is freezed and I have to kill the process.

The issue is very similar to https://github.com/spring-projects/sts4/issues/703 (fixed), but the reported steps to reproduce the issue doesn’t work in my case. I’m trying to figure out a way to reproduce the issue.

I observed that is happening more frequently on a multimodule project using compiler postprocessors (lombok and mapstruct).

Using VisualVM I got the same threaddump of related issue:

"Worker-2: Updating Maven Project" #65 prio=5 os_prio=0 cpu=19453.12ms elapsed=87.52s tid=0x000001c59083b430 nid=0x2c34 in Object.wait()  [0x00000028accfd000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
        at java.lang.Object.wait(java.base@17.0.2/Native Method)
        - waiting on <no object reference available>
        at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:1074)
        - locked <0x0000000766700020> (a java.util.Collections$SynchronizedSet)
        at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedSourceFolderManager.removeFolder(GeneratedSourceFolderManager.java:508)
        at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedSourceFolderManager.folderNamePreferenceChanged(GeneratedSourceFolderManager.java:321)
        at org.eclipse.jdt.apt.core.internal.AptProject.preferenceChanged(AptProject.java:81)
        at org.eclipse.jdt.apt.core.util.AptConfig.setString(AptConfig.java:969)
        at org.eclipse.jdt.apt.core.util.AptConfig.setGenSrcDir(AptConfig.java:917)
        at org.eclipse.m2e.apt.internal.AbstractAptConfiguratorDelegate.configureProject(AbstractAptConfiguratorDelegate.java:171)
        at org.eclipse.m2e.apt.internal.AbstractAptProjectConfigurator.lambda$0(AbstractAptProjectConfigurator.java:95)
        at org.eclipse.m2e.apt.internal.AbstractAptProjectConfigurator$$Lambda$1718/0x0000000801bedcc8.call(Unknown Source)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:364)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:274)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:213)
        at org.eclipse.m2e.apt.internal.AbstractAptProjectConfigurator.configure(AbstractAptProjectConfigurator.java:88)
        at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:123)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$6(ProjectConfigurationManager.java:494)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$$Lambda$1694/0x0000000801b8e4d8.call(Unknown Source)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:364)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:274)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:488)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$4(ProjectConfigurationManager.java:416)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$$Lambda$1693/0x0000000801b8e288.test(Unknown Source)
        at java.util.Collection.removeIf(java.base@17.0.2/Collection.java:576)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:410)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$3(ProjectConfigurationManager.java:340)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$$Lambda$1671/0x0000000801b8d028.call(Unknown Source)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:364)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:274)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:213)
        at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1102)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:339)
        at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:80)
        at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Anyone else out there having the some issue?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

This m2e setting: Preferences > Maven > Annotation Processing > Do not automatically configure/execute annotation processing from pom.xml fixed the issue in my case

using eclipse 2022-12 I got stuck on that “Updating Maven project 75%” message I had to kill eclipse and do: mvn eclipse:clean mvn eclipse:eclipse

then I reopen eclipse and removed the project from IDE, shutdown eclipse and after open it again and imported my project as a maven project, now its working fine

that´s the only way I found to workaround the problem, otherwise eclipse would stay there forever it happens with every new maven project

This m2e setting: Preferences > Maven > Annotation Processing > Do not automatically configure/execute annotation processing from pom.xml fixed the issue in my case

That appears to be the default setting for a fresh install.