Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.4.0
-
None
Description
When saving a LDIF file after making modifications, Eclipse isn't properly notified that the file resource has changed.
Because of that, several ill effects occur until the user manually refreshes (F5) the containing directory of any of ancestor directories:
- the file doesn't appear in team synchronizing perspective if it had an unmodified status before being saved
- search results involving the file aren't updated
- the file doesn't appear in the list of files to be committed to version control system if it had an unmodified status before being saved
- many other
The LDIF editor should generate proper resource modified events.