It's not a secret anymore!
The moose likes IDEs, Version Control and other tools and the fly likes Eclipse - Complete build pain point Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Eclipse - Complete build pain point" Watch "Eclipse - Complete build pain point" New topic

Eclipse - Complete build pain point

Praveen Balaji
Ranch Hand

Joined: Jun 17, 2001
Posts: 60
I have just upgraded to Eclipse 3.0 M9 build. I have a HUGE project opened.

When I make a small change - as small as inserting a new line - and save the project back, it seems to recompile the whole project again. Other tasks have to wait for this to complete.

Can I avoid a complete build everytime a change is made to a file? I think 2.1.3 compiled only the changed files. Am I missing a setting?

Tim West
Ranch Hand

Joined: Mar 15, 2004
Posts: 539
I'm not sure about how much it recompiles, but you can stop automatic rebuilding with Window->Preferences->Workspace->Build Automatically checkbox.

The ability of javac to determine whether or not a class needs recompiling is somewhat limited. I'm not sure of its precise ability, or even whether Eclipse relies on it, but this may be the cause of the huge recompiles.

Certainly in my project (medium sized, ~1500 classes) automatic rebuilding is not a feasible option. I just do Ctrl-B when I want a new build. It kinda gets you into a "code for a bit, fix typos for a bit, review for a bit" mentality when coding.


I agree. Here's the link:
subject: Eclipse - Complete build pain point
It's not a secret anymore!