Avoid merging old Groovy source-class mappings on full recompilation #9936
Currently, if we're doing a full recompilation in some cases, we still merge the new mapping into the old mappings - this might cause problems, for example, the old mapping:
the new mapping:
The merged mapping:
When constructing a reverse mapping, something bad happens: which file should
So we'd better fully clean up the mapping on full-recompilation.