Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Eclipse loops endlessly: Invoking 'Maven Project Builder'

Ugh! My Eclipse is stuck in an endless loop:

  • No operations to display at this time
  • Refreshing Workspace Building
  • Workspace. Invoking 'Maven Project Builder' on /MobileWebApp

The building workspace never gets past 58%.

Details:

Google's GWT provides a sample app MobileWebApp. They suggest adding it to Eclipse via File > Import > Checkout Maven projects from SCM.

I followed the instructions in this blog for adding the plugins for m2e, subclipse, and the m2e-subclipse connector.

After installing the plugins, I imported the sample project via File > Import > Checkout Maven projects from SCM and this URL.

The import seemed to complete ok and Eclipse doesn't display any markers. But now I have this endless refreshing and building and have no clue what is causing it or how to fix it.

Versions:

  • Eclipse Indigo 3.7
  • m2e 1.0.100
  • m2e connector for build-helper-maven-plugin 0.14
  • Maven SCM handler for Subclipse 0.13
  • Subclipse 1.6.18
  • Subclipse Client Adapter 1.6.12

Any advice is greatly appreciated.

like image 257
Justin Avatar asked Nov 14 '11 01:11

Justin


People also ask

Why does Maven build failure in eclipse?

The error message indicates that Maven is unable to find the Java compiler, which comes only with a JDK and not with a JRE.

Why is Eclipse Building workspace so slow?

In development, when you find the eclipse workspace build process is slower and slower, and if the main reason is because of validating static files ( for example validate JS, CSS, XML file, and so on). Then you need to reduce or remove the validators in the eclipse preference validation section.


2 Answers

I opened my module's .project file. There were two entries:

<buildCommand>   <name>org.maven.ide.eclipse.maven2Builder</name> </buildCommand> <buildCommand>   <name>org.eclipse.m2e.core.maven2Builder</name> </buildCommand> 

I removed org.eclipse.m2e.core.maven2Builder entry and it magically fixed the problem.

like image 166
Fred Campos Avatar answered Oct 09 '22 23:10

Fred Campos


I was able to resolve this by right clicking on the project and selecting Run As > Maven Clean

like image 20
Justin Avatar answered Oct 09 '22 21:10

Justin