Menu
Normally when we check Project->Build automatically, it will build when our project's source has change, But when i check this option my eclipse is always building-- about every 2 or 3 seconds-- no matter it has changes or not. I can see from the right bottom state bar show "building workspace...".
It's annoying that this behavior drive my eclispe really slow and the CPU is always in high usage.
I'm using eclipse 3.7 for java EE developers, m2e, maven integration for WTP, git plugin, subclipse and Google plugin for eclipse, checkstyle, findbugs, etc.
Any ideas?
P.S I'm on Win 7 with 8GB RAM
709
In these situations, autobuild can be turned off through Window > Preferences > General > Workspace > Build automatically. Even for smaller workspaces, turning off autobuilding may be a useful feature.
It means Eclipse is rebuilding every relevant project in your namespace.
By default, you are in auto-build mode and Eclipse takes care of compiling source files automatically. Builds occur automatically in the background every time you change files in the workspace (for example saving an editor). Auto-build is convenient because it means problems view, binaries, etc.
How To Solve Eclipse Building Workspace Too Slow Problem 1. Uncheck Project Auto Build.. If you check the project auto-build menu item, the project will build automatically... 2. Increase Eclipse Used Memory Size.. Eclipse used maximum and minimum memory size are configured in eclipse.ini file. 3. ...
About Eclipse Workspace. The workspace has a hierarchical structure. Projects are at the top level of the hierarchy and inside them you can have files and folders. Plug-ins use an API provided by the resources plug-in to manage the resources in the workspace.
The eclipse workspace contains resources such as − The workspace has a hierarchical structure. Projects are at the top level of the hierarchy and inside them you can have files and folders. Plug-ins use an API provided by the resources plug-in to manage the resources in the workspace.
So you can make your eclipse project far away from hanging by following two methods. Create a new workspace and import all existing projects into it. Close the current workspace and delete the .metadata folder under the current workspace and open the workspace again in eclipse to create a new .metadata folder.
I have seen this effect with an ant-based build before.
You probably have something in your maven build that outputs to one of the source folders or one of it subdirectories. Eclipse detects that a file has changed and starts a new build.
173
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
