开发者

Symfony2 Eclipse plugin, so hard to get it working?

My setup is a fesh install of Eclipse Classic 3.7.1 plus Symfon开发者_C百科y2 plugin from its update site:

  • My workspace is C:\Users\Marco\Documents\Eclipse.
  • I've extracted Symfony_Standard_Vendors_2.0.4.zip inside it (a new folder Symfony2 ws created).
  • Then i created a Symfony2 project (path to C:\Users\Marco\Documents\Eclipse\Symfony2)
  • I've modified PHP build path of my project (as explained here) to include app, src and vendor folder.

Result: hundred of validation errors mainly because of vendor folder, as the plugin was completely ignored. Auto-complete works only in PHP classes but not in Twig files.


at the time of your writing the plugin was still alpha. please report any issues you encounter with the plugin on github (https://github.com/pulse00/Symfony-2-Eclipse-Plugin) otherwise i can't investigate the problem. thanks


In Eclipse Project Properties, Validation section: - Enable Project specific settings - Select XML Schema Validator Settings ("..." button) - add exclude group - add a rule to "exclude group" which excludes doctrine/orm/doctrine-mapping.xsd


Some errors like

cos-nonambig: WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"] and WC##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping" violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.

are not coming from the Symfony2 Eclipse Plugin. It's XML/XSD validation errors that occur because those xsd/xml files are invalid from the Eclipse's XML/XSD validator point of view. If you exclude these folders from the build path, the PHP Indexer/Parser won't visit those folders, but Eclipse's XML/XSD validator still check them.

For more information, check out this issue on pulse00's Github and this other one on Symfony's official Github.

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜