Community
Participate
Working Groups
When Java file changed outside of eclipse and is not opened in editor inside eclipse, in order to build the file, whole project has to be rebuilt. Ctrl+B will not build the file. If file is opened inside eclipse and changed outside, then eclipse will ask whether to reload it and will mark it as dirty. Additional nice to have: If you have more than one file opened inside eclipse and modified outside of it, it would be nice to have a single dialog or a series of dialogs that happen automatically without need to refocus on every open file inside eclipse.
Instead of rebuilding all, simply use the 'refresh' action from package view. It will force to detect such changes, and if in auto-build, an incremental build action will automatically be triggered if necessary. Does this do the trick for you ?
From reporter: Yes, but: First: I have to use mouse to do that, and that is tedious. Second: I want the eclipse to be able to automatically absorb all external changes. (Much quicker too). So, for this to be effective, I think there is a need for user modifyable setting, where all changes will be automatically recognized, whether file is open inside eclipse or not. That's how good programming editors work. Regarding need to manually refresh: I'm sorry, JBuilder does not require that. And if they can do it, you can! So it's a bug!
This would be a platform feature request then.
Give the auto-refresh plug-in a try. See referenced bug report for details. *** This bug has been marked as a duplicate of 14867 ***
