Eclipse需每次执行Project>Clean才能运行最新代码的解决方法及原因问询

Hey there, I’ve dealt with this exact Eclipse headache before—nothing’s more annoying than debugging a "bug" that turns out to be just old code running! Let’s walk through your questions clearly:

1. Setting Up Automatic Cleaning to Skip Manual Project > Clean #

First, let’s start with the simplest fix that solves this 90% of the time:

• Enable Build Automatically: Head to the top menu bar, click Project, and make sure Build Automatically has a checkmark. This tells Eclipse to recompile your code every time you save, so it won’t hang onto old class files.
  If that still doesn’t stop the old code from running, you can force Eclipse to clean before each build:

1. Right-click your project → Properties → Builders.
2. Select the Java Builder and hit Edit.
3. Go to the Build Options tab, then check the box for Clean projects before full build (the wording might vary slightly depending on your Eclipse version).
   One more thing: Go to Window > Preferences > General > Workspace and make sure Refresh using native hooks or polling is turned on. This helps Eclipse detect file changes more reliably, so it doesn’t miss updates that need compiling.

2. What’s Causing This Frustrating Issue? #

Here are the most common reasons Eclipse keeps running old code:

• Automatic Build is Disabled: If Build Automatically is off, Eclipse won’t recompile your changes when you save. So even if you write new code, it’s still using the last compiled version until you manually build or clean.
• Corrupted Workspace Metadata: Eclipse stores build state, cache, and workspace settings in the .metadata folder. Over time, this can get corrupted, leading to mismatches between your source code and the compiled class files in the bin/ folder.
• Output Folder Conflicts: Sometimes old class files in the bin/ directory don’t get overwritten—this could be due to file permissions (if Eclipse can’t write to the folder), or if your build path is set to include external class files that take precedence over your local ones.
• Glitchy Incremental Build: Eclipse’s incremental build system is supposed to only recompile changed files, but it can glitch out (especially with nested classes, resource files, or after large refactors). When this happens, it skips compiling updated code, leaving old class files intact.

3. Why Don’t IntelliJ Colleagues Have This Problem? #

It boils down to fundamental differences in how the two IDEs handle builds and caching:

• Default Automatic Build: IntelliJ IDEA enables Make Project Automatically by default (find it in File > Settings > Build, Execution, Deployment > Compiler). Its incremental build system is more robust—it tracks every change to your source files and ensures new class files always replace old ones.
• Smarter Cache Management: IDEA’s cache system automatically invalidates old data when you make changes, so it never relies on stale compiled files. It also separates build outputs more cleanly, reducing the chance of old files lingering.
• Project-Specific Configuration: Unlike Eclipse, which uses a single .metadata folder for the entire workspace, IntelliJ stores project-specific settings separately. This means if one project has a build issue, it doesn’t affect others, and metadata corruption is less likely to cause widespread build problems.

内容的提问来源于stack exchange，提问作者A. Neo