Closed theofidry closed 8 years ago
Actually even with rm the sub/vendor
it still failed, or rather, the json was merged but it all the deps were not installed correctly and running an update a second time solved the issue...
The specific message you quote seems to be from your fork of composer-merge-plugin. Can you provide a details example that reproduces the issue using the plain composer-merge-plugin? Ideally this will be a set of composer.json files and exact cli instructions used along with the version of Composer and composer-merge-plugin that are being used.
I couldn't reproduce the issue even with my plugin in an isolated environment. It's possible it's due to a weird machine state or something. Is there any cache done somewhere in the plugin? Anyway closing this, will re-open if I can find anything on it.
composer.json
with a depsub/composer.json
withwikimedia/composer-merge-plugin
referencing the parentcomposer.json
composer update
for bothcomposer.json
And then if you add a dependence on the root,
composer.json
, runningcomposer update
on the child will give[inheritance-plugin] Already merged ../../composer.json
so the new dep added to the root won't be added to the child.