作曲家更新后@template注释出现问题

时间:2019-03-25 08:31:02

标签: symfony doctrine sylius

我在Sylius项目中将Doctrine更新为最新版本。更新后,我收到以下错误。

[Semantical Error] The annotation "@template" in class Doctrine\Common\Collections\ArrayCollection was never imported. Did you maybe forget to add a "use" statement for this annotation?

有人可以帮助我吗?

更新日志:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 3 installs, 5 updates, 0 removals
  - Updating doctrine/collections (v1.3.0 => v1.6.0): Loading from cache
  - Installing doctrine/reflection (v1.0.0): Loading from cache
  - Installing doctrine/event-manager (v1.0.0): Loading from cache
  - Installing doctrine/persistence (v1.1.0): Loading from cache
  - Updating doctrine/common (v2.8.1 => v2.10.0): Loading from cache
  - Updating doctrine/dbal (v2.6.3 => v2.9.2): Loading from cache
  - Updating doctrine/orm (v2.5.14 => v2.6.3): Loading from cache
  - Updating symfony/doctrine-bridge (v4.1.11 => v4.2.4): Loading from cache
Package phpunit/phpunit-mock-objects is abandoned, you should avoid using it. No replacement was suggested.
Package symplify/token-runner is abandoned, you should avoid using it. Use https://github.com/symplify/codingstandard instead.
Writing lock file
Generating autoload files
muglug/package-versions-56:  Generating version class...
muglug/package-versions-56: ...done generating version class
ocramius/package-versions:  Generating version class...
ocramius/package-versions: ...done generating version class

What about running composer thanks now?
This will spread some   by sending a ★  to 271 GitHub repositories of your fellow package maintainers.

Executing script cache:clear [OK]
Executing script assets:install public [OK]

4 个答案:

答案 0 :(得分:2)

当自动更新学说/集合(v1.5.0 => v1.6.0)时,我遇到了相同的错误。 尝试使用v1.5.0版本。

答案 1 :(得分:0)

同样的问题,这似乎是您的require或require-dev中的依赖项之一已损坏。尝试仅升级您需要的依赖项。如果您升级一个版本,但由于该错误而失败,请将该错误报告给维护人员。

答案 2 :(得分:0)

是的-如果您将软件包学说/集合降级到1.5版,则一切正常。

以下是一些信息:

https://github.com/doctrine/collections/issues/180

答案 3 :(得分:0)

此问题已在1.6.1版本中修复。只需运行composer update即可解决。有关更多信息,请参见版本详细信息here