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

remove composer.phar from legacy folder #40

Open
pavarnos opened this issue Apr 25, 2016 · 0 comments
Open

remove composer.phar from legacy folder #40

pavarnos opened this issue Apr 25, 2016 · 0 comments

Comments

@pavarnos
Copy link

Hi

It should be Ok to remove composer.phar from your /legacy/ folder as most people have it separately installed these days. It causes problems in editors like phpStorm because composer.phar has declarations for some widely used Symfony components, so phpStorm reports duplicate class declarations unless you manually go and exclude each composer.phar from your project after each update.

Also, is it possible for you to tag a new release of grandt/relativepath so that composer will pick up that you have deleted composer.phar from there when including it as a dependency of grandt/phpepub?

thanks!

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

1 participant