Question

I have lost more time than I care to relate from testing worthless builds resulting from unsaved code changes. I have searched the web for the magic setting I need to change & none work. My workflow is this:

1. make code changes
2. invoke ant build by double-clicking on target in ant window
3. hate life because code changes were not saved, and hence not included in build

There must somewhere be some trigger that detects an ant target invocation & prompts (or not, configurably) to save all dirty editors. Please, if anyone knows, tell me what it is.

Answer 1

Does this bug sound like what you’re seeing?

Launch External Tool does not save dirty editors regardless of preference setting