Bug #44496
New doctrine.annotations classes are proxied but should not
| Status: | Resolved | Start date: | 2013-01-14 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 2.1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | Affected Flow version: | Git master |
Description
doctrine.annotations was moved out of Doctrine.Common and so aren't excluded from object management anymore. With that fatal errors occur even when just calling the flow command.
Associated revisions
[BUGFIX] Exclude Doctrine Annotations and Collections from reflection
Doctrine split Annotations and Collections from the Common package,
now the exclusion of those packages from reflection is updated.
Change-Id: Ia79ed82c7d68479b15dfe10c80f9d96d571017a9
Fixes: #44496
Releases: master
[BUGFIX] Lock Doctrine ORM to version 2.3.x
This change locks the Doctrine ORM to version 2.3.x to avoid unwanted
changes from sneaking in.
To be on the safe side, YAML and Dom Crawler from Symfony are locked
down as well (2.1.x and 2.2.x respectively).
Change-Id: Ia79ed82c7d68479b15dfe10c80f9d96d571017a9
Fixes: #44496
Fixes: #44479
Releases: 2.0
History
#1 Updated by Karsten Dambekalns over 2 years ago
- Category set to Persistence
- Assigned To set to Karsten Dambekalns
- Target version set to 2.1
- Affected Flow version changed from (any) to Git master
#2 Updated by Karsten Dambekalns over 2 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Pushed directly to master (by accident).