Panasonic Youth rob sanheim writes about software, business, ruby, music, stuff and things

Eclipse tip: always save automatically to stay in the flow

I almost never want to be asked if I want to save an editor window in Eclipse. With the safeguards of version control and local history, there is never a save that cannot be reverted easily. When I’m really in the flow, I want the cycle to be seamless between edit test case, ctrl-f11 (run test), modify code under test, ctrl-f11 (run test), etc…. Having a window popup after each little code modification is very annoying and slows you down.

If you check the following preferences, you should almost never be asked for confirmation for save. The only time I still get asked is if I close an editor window that hasn’t been saved, as I haven’t found a auto save option for it yet. So, go check these preferences in Eclipse:

Always save before building (Eclipse will auto build before launching and running tests).

Always save before launch (ie before running Junit tests or your test server).

Finally, auto save before doing any refactoring, so things are in a consistent state.

i actually like IDEA’s default behavior on this issue. i wish eclipse would have this. it saves the files on any focus change on screen. i dont remember saving stg manually for years.

Yeah that sounds like what I want. I basically want it to save whenever I change anything, so there is never an interruption of the test-run-refactor cycle.

can you help me to auto build properties file.
Struts Project
i’m use Properties editor plugin to view properties file
When i’m saving file it not auto build this file. I must clean project and build again.
Can you help me