Composer Path Repositories without a package manager #11240
-
|
This is a duplicate of https://stackoverflow.com/questions/74891412/composer-path-repositories-without-a-package-manager Since composer merge plugin is deprecated and the alternative is use of composer path repositories I found a problem transitioning to the later. My structure is: /composer.json /local/composer.json Where /composer.json is main composer with all setup and /local/composer.json is a file managing only private repositories. Contents of each file are: As you can see the plan is simple: main composer requires sub/project and sub/project requires rotari/test_repo. However on install I'm prompted with error sub/project dev-main requires rotari/test_repo dev-main -> could not be found in any version Running composer install in /local is a success so there is no problem accessing rotari/test_repo. Any idea or suggestions how this issue could be solved? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Repositories can only be defined at the root: https://getcomposer.org/doc/faqs/why-cant-composer-load-repositories-recursively.md |
Beta Was this translation helpful? Give feedback.
-
|
Well, that answers it. |
Beta Was this translation helpful? Give feedback.
Repositories can only be defined at the root: https://getcomposer.org/doc/faqs/why-cant-composer-load-repositories-recursively.md