score:27

Accepted answer

Turns out bug 27940 hasn't been fixed yet.

I use the following workaround:

  1. Disable "Project > Build Automatically"
  2. Project > Clean
  3. Project > Build All

score:0

Apart from building all project you can Close the projects that are finished.
click on the finished project and
go to
project ->close project
hope this will work

score:0

Both projects are referenced to each other.

Go to "Project->Properties->Project References" and check the references on both projects, that causes like an endless loop when building automatically.

score:0

In my case this could be solved in the following way:

I had a command line window open with the current directory set into a target-folder of the projects to be build. That caused the infinite loop. Closing the window and problem solved.

I guess, that if something prevents eclipse to remove some target folder, it will try over and over again.

score:0

I had the same problem and resolved it by remove: Project > Properties > Builders > JavaScript Validator

I had no javascript on my webapp.

score:0

To add my two cents: Yes, it's 2019, so Eclipse 2019-06 is installed now... eyeroll I mean I occasionally had the problem with earlier versions, too, but after upgrading to Eclipse 2019-06 I suddenly had three such "sleepers" running in parallel and wasn't able to do anything any more.

To make it work again I had to delete the directory tree of my projects in my Maven repository. So in my case I only had to delete the directory ~/.m2/repository/com/sjngm.

Then I restarted Eclipse and during the start-up it seemed to download the now missing dependencies underneath that directory from our internal repository.

score:1

I had this same issue pop up for me and for awhile I couldn't figure out why. Then I finally figured out what was causing it (for me anyway).

It turns out I had an old project in my workspace that uses one of my custom libraries but the build path was not setup properly to use the library (its a shame Eclipse couldn't simply tell me that!). I had copied this workspace from another hard drive and I guess the file paths were all different now.

So, if any of your projects in your workspace use any external libraries make sure the build path has your library defined (Properties -> Java Build Path -> Projects[tab].

I hope that helps someone else.

score:2

I solved it by opening my module's .project file. There were two redundant entries and deleting one helped:

<buildCommand>
    <name>org.eclipse.m2e.core.maven2Builder</name>
    <arguments>
    </arguments>
</buildCommand>
<buildCommand>
    <name>org.eclipse.m2e.core.maven2Builder</name>
    <arguments>
    </arguments>
</buildCommand>

Sometimes it can also be caused by the following two entries from which you have to remove the older org.maven.ide entry

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

It may also be that there are two identical natures:

<natures>
    <nature>org.eclipse.m2e.core.maven2Nature</nature>
</natures>
<natures>
    <nature>org.eclipse.m2e.core.maven2Nature</nature>
</natures>

or two natures from which one is old

<natures>
    <nature>org.eclipse.m2e.core.maven2Nature</nature>
</natures>
<natures>
    <nature>org.maven.ide.eclipse.maven2Nature</nature>
</natures>

Just delete the redundant one or the old org.maven.ide.eclipse.maven2Nature

score:3

Did you add your workspace to a Windows 7 library (i.e. the Windows Explorer Favorites or Windows Explorer Libraries)? Another user had a similar issue here.

If you have something open in a different editor (in the target directory of your project), this can also cause an infinite "Build Workspace" loop.


Related Query

More Query from same tag