We are using JRebel to quickly reload Java code changes into our JVM. This is working great!

But, we are also using Eclipse as IDE. And for some reason, Eclipse can really rebuild the whole project in my workspace, just because I add an annotation, I remove a method, or any other little code change ...
Because of this rebuild phase, all classes are regenerated and are required to be reloaded by JRebel.

Is there *any* way to debug why Eclipse is always rebuilding our project for even a stupid little code change?
I'm using Eclipse Indigo.

Thanks,
Jochen