I don't mean to be rude but this is very important to me.
The following bug
has been closed recently with "Do not fix" remark and I don't understand why.
Since when and why seeing a stale content (that is, the old content of a file modified concurrently by another application) and failure to notify about content change is considered a "feature", not a bug? Does anyone care to explain?
I'm generating a lot (hundreds) of java source, configuration and other files automatically during development/build process and having to see stale content is a real pain. Besides, I don't see any problems fixing it (Please correct me if I'm wrong). It must be a half-an-hour work or less.
I wouldn't be so demanding if the problem was in an EAP build, but this is in production build I've paid for. I think that bugs in production builds must have priority.
I do confirm also that this is working correctly in IDEA-2.6 (I have it reinstalled). So all I'm asking is to restore the correct bahavior.
I'm sorry for such a request but, again, this makes my life miserable. Hope to hear from you soon, Oleg