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

Why are you committing the composer phar ? #108

Open
stof opened this issue Oct 6, 2015 · 0 comments
Open

Why are you committing the composer phar ? #108

stof opened this issue Oct 6, 2015 · 0 comments

Comments

@stof
Copy link

stof commented Oct 6, 2015

This creates issues with IDEs when using PhpStorm to work on Packananlyst for instance, because it finds the class definition for composer files multiple times:

  • in vendor/composer/composer where composer got installed as a dependency
  • in vendor/mouf/mouf/composer.phar because PhpStorm is smart enough to analyze phars

There are ways to make it ignore the phar, but this practice looks weird (and your phar is old btw, as it is from December 2014)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants