Description
The symbol cache doesn't update itself anymore when changing files after a project update (like changing the pom.xml) file. The reason for that is that the cache key for the beans is calculated from the classpath entries and this computation includes the output folders of a project.
While this is not totally wrong on its own, the timestamp of the output folders are changed in a somewhat unpredictable fashion. In the case described above it appears to be the case that the timestamp of the output folder is changed after the first Java source file save event after a project update. That causes the confusion that the symbol machinery gets a single file update event (for the changed java source file), but the cache key is different from what the symbol cache knows about from the project update event.
The solution to this is to not include the output folders in the cache key computation anymore - which doesn't make a lot of sense anyway since the source files are tracked in the symbol cache anyway.