A backwards-compatibility layer has been added to persistence to helpconsumers move to the new namespacing. It is based on class aliases,which means the type declaration changes should not be a BC-break: typesare the same.Seedoctrine/persistence#71This means:- using the new namespaces- adding autoload calls for new types to types that may be extended anduse persistence types in methods signatures for which compatibilitychecks may happen,so that signature compatibility is recognized by old versions of php.More details on this athttps://dev.to/greg0ire/how-to-deprecate-a-type-in-php-48cfFixesdoctrine#616 as a side effect, but the real fix is atsymfony/symfony#35728

A backwards-compatibility layer has been added to persistence to helpconsumers move to the new namespacing. It is based on class aliases,which means the type declaration changes should not be a BC-break: typesare the same.Seedoctrine/persistence#71This means:- using the new namespaces- adding autoload calls for new types to types that may be extended anduse persistence types in methods signatures for which compatibilitychecks may happen,so that signature compatibility is recognized by old versions of php.More details on this athttps://dev.to/greg0ire/how-to-deprecate-a-type-in-php-48cfFixesdoctrine#616 as a side effect, but the real fix is atsymfony/symfony#35728

A backwards-compatibility layer has been added to persistence to helpconsumers move to the new namespacing. It is based on class aliases,which means the type declaration changes should not be a BC-break: typesare the same.Seedoctrine/persistence#71This means:- using the new namespaces- adding autoload calls for new types to types that may be extended anduse persistence types in methods signatures for which compatibilitychecks may happen,so that signature compatibility is recognized by old versions of php.More details on this athttps://dev.to/greg0ire/how-to-deprecate-a-type-in-php-48cfFixesdoctrine#616 as a side effect, but the real fix is atsymfony/symfony#35728

This PR was merged into the 4.4 branch.Discussion----------Add missing autoload callsUntil either php 7.4 or doctrine/persistence 2 is required, these willbe needed to make sure php recognises signatures using the old names ascompatible with signatures using the new names.This is necessary for types defined outside Symfony that extend typesfrom Symfony and still use the old names in signatures of methods theyoverride.Fixesdoctrine/DoctrineMongoDBBundle#616| Q             | A| ------------- | ---| Branch?       | 4.3| Bug fix?      | yes| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->| Tickets       |Fixdoctrine/DoctrineMongoDBBundle#616| License       | MIT| Doc PR        | n/a<!--Replace this notice by a short README for your feature/bugfix. This will help peopleunderstand your PR and can be used as a start for the documentation.Additionally (seehttps://symfony.com/releases): - Always add tests and ensure they pass. - Never break backward compatibility (seehttps://symfony.com/bc). - Bug fixes must be submitted against the lowest maintained branch where they apply   (lowest branches are regularly merged to upper ones so they get the fixes too.) - Features and deprecations must be submitted against branch master.-->This topic is fairly complicated, more details athttps://dev.to/greg0ire/how-to-deprecate-a-type-in-php-48cfCommits-------94b5dbd Add missing autoload calls

A backwards-compatibility layer has been added to persistence to helpconsumers move to the new namespacing. It is based on class aliases,which means the type declaration changes should not be a BC-break: typesare the same.Seedoctrine/persistence#71This means:- using the new namespaces- adding autoload calls for new types to types that may be extended anduse persistence types in methods signatures for which compatibilitychecks may happen,so that signature compatibility is recognized by old versions of php.More details on this athttps://dev.to/greg0ire/how-to-deprecate-a-type-in-php-48cfFixesdoctrine#616 as a side effect, but the real fix is atsymfony/symfony#35728

…ire)This PR was merged into the 5.2 branch.Discussion----------[DoctrineBridge] Require doctrine/persistence 2| Q             | A| ------------- | ---| Branch       | 5.x| Bug fix      | no| New feature  | no <!-- please update src/**/CHANGELOG.md files -->| Deprecations | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->| Tickets       | n/a| License       | MIT| Doc PR        | n/aThis allows us to remove autoload calls that are necessary for thepersistence 1 backwards-compatibility layer to work.This is a follow up of#35728Commits-------574a184 Require doctrine/persistence 2