Skip to content

Why are you committing the composer phar ? #108

Open
@stof

Description

@stof

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)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions