Eclipse loops endlessly: Invoking 'Maven Project Builder'

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.

Answer by Justin for Eclipse loops endlessly: Invoking 'Maven Project Builder'

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

Answer by Abhi for Eclipse loops endlessly: Invoking 'Maven Project Builder'

it some times worked for me when i change my JAVA_HOME to a new location

Answer by Fred Campos for Eclipse loops endlessly: Invoking 'Maven Project Builder'

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

    org.maven.ide.eclipse.maven2Builder        org.eclipse.m2e.core.maven2Builder    

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

Answer by Chris Hinshaw for Eclipse loops endlessly: Invoking 'Maven Project Builder'

I actually solved the problem that was caused by the jaxb plugin. If the forceRegenerate is set to true you will get the build loop in eclipse (Kepler in my case).

Verify that you have forceRegenerate set to false in your maven-jaxb-plugin.

                                        false    

Answer by Amos M. Carpenter for Eclipse loops endlessly: Invoking 'Maven Project Builder'

I was getting the same issue in an eclipse (Juno) Maven project that had nothing to do with GWT - it just kept refreshing and "Invoking Maven Project Builder". Going to the Progress view and requesting a cancellation of either progress entry (by clicking that red stop button on the right) didn't help.

The project the builder kept getting stuck on was always the same, and a couple of levels deep in a set of multi-pom maven projects in eclipse.

What eventually solved it for me was just going into that particular project's Properties > Builders and unchecking Maven Project Builder (but keeping the Java Builder checked so that it would still auto-build when code changed). I just ignored the warning about this being an "advanced operation" and possibly having "many side-effects" - I figured it couldn't be any more annoying than that constant build-refresh cycle. I'm still not sure what the cause of this loop was, but that stopped it for me. And I haven't had any problems since.

Answer by Lonzak for Eclipse loops endlessly: Invoking 'Maven Project Builder'

I opened my module's .project file. There were two redundant entries and deleting one helped

      org.eclipse.m2e.core.maven2Builder                      org.eclipse.m2e.core.maven2Builder                

Answer by 99Sono for Eclipse loops endlessly: Invoking 'Maven Project Builder'

M2e, even in eclipse mars, seems to like infinite building.

In my case, no such thing as repeated build commands, as listed bellow. The only thing that seems to work when the project tree is gigantic is:

1. open eclipse
2. Disable build automatically as soon as you open eclipse
3. refresh the workspace and trigger manual a Crtl+B or a build all.
4. Once eclipse is satisfied that it build the full project tree ... better have four core machine or you're gonna be waiting a while, you can finely put the build automatically option active. Eclipse seems not to go in a building spree after that. It will still go for a while scanning some folders, but activating the build automatically - once you've built it all before - is much faster than a new build all, and finally, eclipse becomes stable stops building infinitely.

Otherwise, you're stuck with the deprecated mvn eclipse:eclipse ... and have to abandon the use of maven commands from within eclipse echosystem. M2e seems to have a really gigantic hard time cooperating with the beast.

I still use m2e, but must say it is 100 times more difficult to swallow m2e than maven integration in netbeans. On the otherhand, eclipse is much faster for very large code base. Pick your poison, you'll always get bitten.

                 rootPom                                                                        org.eclipse.m2e.core.maven2Builder                                                                                    org.eclipse.m2e.core.maven2Nature                  

Fatal error: Call to a member function getElementsByTagName() on a non-object in D:\XAMPP INSTALLASTION\xampp\htdocs\endunpratama9i\www-stackoverflow-info-proses.php on line 72