Jira issue originally created by user giorgiosironi:
As you can see in:
mappingNotFound() accepts now only 1 argument, but is called with 2; this leads to cryptic errors when the a field does not exist like:
Doctrine\ORM\Mapping\MappingException: No mapping found for field 'EntityClassName'
Comment created by @beberlei:
Issue was closed with resolution "Fixed"