Drop packages available stand-alone

[alcaeus]

With the migration to persistence 2.0 requiring a new major release, it would be a good time to drop all packages that we've extracted into standalone packages. This keeps necessary functionality (e.g. proxy logic) around and supported, while at the same time removing the need for future major releases when another package (e.g. Annotations, Collections, etc.) release a new major version.

Note that we have for a while suggested that people don't rely on doctrine/common for functionality like annotations, inflector, etc., so this BC break in a major release should not be a big burden on the ecosystem.

Regardless, packages still depending on doctrine/common are encouraged to depend on "doctrine/common": "^2.13 || ^3.0" as well as the package for the functionality they need while we make this transition.

[greg0ire]

You can get a stack trace for the deprecation by using SYMFONY_DEPRECATIONS_HELPER=/toString/

[stof]

I'm totally in favor of this change.

[alcaeus]

The deprecations were caused due to using lowest dependencies in the lock file, which means testing PHPUnit 7.0 on PHP 7.4. I've removed the lock file altogether and added a build stage to test against lowest deps. Everywhere else we now test highest deps.

[stof]

why using --prefer-source (while persisting the composer cache in the Travis cache at the same time) ? Using --prefer-dist will benefit from the persisted cache.

[SenseException]

BTW: Using --no-interaction is more descriptive than just -n and makes the travis-file easier to read.

[alcaeus]

Good point. I’ll update this 👍