Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=130057.
This is an adopter hot bug in which
resource deletes do not remove the virtual component mapping from the virtual
resource file cache. So, this can cause a number of issues, for example,
the resource mapping in the .component is saved back out unexpectedly or
on publish, deploy will try and find a non existing file.
The fix was to ensure on the remove
notification that the child resource mapping was removed from the virtual
resource tree map. This was not happening because it was trying to
retrieve based on the new value rather than the original old value. See
the defect for more information. Junits and unit tests pass and code
has been reviewed.
Software Engineer, IBM Rational
"I know this lady way down in my country.
She is so pretty that my eyes throw disguises at me.
Now we will sit and we'll wonder about our future,
But now I'm thinking that today sounds fine to me." - Of A Revolution