Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors adding Symfony nature #52

Closed
DiUf opened this issue Nov 2, 2011 · 1 comment
Closed

Errors adding Symfony nature #52

DiUf opened this issue Nov 2, 2011 · 1 comment

Comments

@DiUf
Copy link

DiUf commented Nov 2, 2011

Hello, I'm new in eclipse and symfony. I just installed Eclipse and the plugin for Symfony 2, all right, but creating a new project and adding the Symfony nature, I get the following 5 errors:

cos-nonambig: WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"] and WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"](or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. doctrine-mapping.xsd /gcc/vendor/doctrine line 113 XML Schema Problem

cos-nonambig: WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"] and WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"](or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. doctrine-mapping.xsd /gcc/vendor/doctrine line 371 XML Schema Problem

Description Resource Path Location Type
cos-nonambig: WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"] and WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"](or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. doctrine-mapping.xsd /gcc/vendor/doctrine line 389 XML Schema Problem

cos-nonambig: WC[##other:"http://symfony.com/schema/dic/services"] and WC[##other:"http://symfony.com/schema/dic/services"](or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. services-1.0.xsd /gcc/vendor/symfony/src/Symfony/Component/DependencyInjection/Loader/schema/dic/services line 20 XML Schema Problem

cvc-complex-type.2.3: Element 'routes' cannot have character [children], because the type's content type is element-only. routing.xml /gcc/vendor/bundles/Sensio/Bundle/GeneratorBundle/Resources/skeleton/crud/config line 5 XML Problem


I have excluded at the buildpath app/cache, app/logs and vendor/...GeneratorBundle.../skeleton folders.

Thank you very much.

@pulse00
Copy link
Owner

pulse00 commented Nov 2, 2011

If you create new projects, you don't need to add the natures yourself, just use the "New Symfony Project" wizard. If you want to create a project from existing sources, than you need to manually add those natures.

However, the validation errors you posted are not coming from my plugin, it's XML/XSD validation errors that occur because those skeleton xsd/xml files are invalid from the XML/XSD validator point of view.

If you exclude folders from the build path, that only means that the PHP Indexer/Parser won't visit those folders, but all the other built-in validators still check them.

I have not found a solution for this problem yet, though i think you can somehow manually exclude folders from the XML/XSD validation too.

I'll investigate if it's possible to exclude those directories from XML validation programmatically somehow, so this can be automated too.

@pulse00 pulse00 closed this as completed Nov 13, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants