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!
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!