Clever Geek Handbook

How do I know why Eclipse is stuck in an infinite build loop?

I have an Eclipse building a Maven project that I just imported. I have an automatic build check and Eclipse builds constantly. It builds and waits for a few seconds and builds again, without any changes. I noticed that this only happens when the server is running, so I'll include some setup information here:

  • You have a local Tomcat installation.
  • Eclipse is configured to start Tomcat, but points the Tomcat binaries to their own directory (Server Location is set to Use Workspace Metadata).
  • Eclipse is set to "Automatically publish when resources change".

As far as I know, Eclipse (or Eclipse embedded Maven) builds everything into a target directory at the root of my project. Is it possible that Eclipse doesn't understand that the target directory shouldn't be scanned for changes?

There are null references checked in project properties -> Project references.

I do not understand what it could be. If there are other settings that someone would like to confirm with me, please let me know.

This seems to be the same problem, but none of the answers seem to apply to me. I'm not sure what the original poster's comment means that "added annotation processing to my project that interferes with the build process".

+3


source to share


1 answer


Is your code generating something in src / main / java or src / main / resources? Only then can the eclipse scanner interpret this as "source change" and then build and deploy continuously.



Any change to 'src' should trigger a build Any change to a "target" should trigger a deployment. If your code is generating target data (for example for logging), you will see tomcat deploy continuously

+2


source






More articles:


All Articles