Conversation
Avoid nested duplication if a module folder exists when using copy strategy
|
Can confirm the duplication while copy deployment strategy I wonder why this happens now. What changed, that this occurs? |
|
@olythy How can I test your changes? |
|
Hi, I have a fork here https://github.com/mage-better-m1/magento-composer-installer Could you reproduce the problem? |
|
@olythy I tried your fork: I deleted composer.json: composer.lock: But it did not fixed the problem. I still have nested duplication |
|
For better testing: result: htdocs/app/code/community/AvS/MissingTranslations/MissingTranslations/ Ich will try to generate a minium composer.json to reproduce this bug |
|
I tried installation with this minimal composer.json - and it worked fine! composer.txt Maybe, the problem with nested duplication is something like a "sideeffekt" from other modules & dependencies. |
|
After this minimal composer.json I added Then I deleted Now, Avs/MissingTranslations becomes a nested duplicate. CLI outputs: composer require aoepeople/aoe_scheduler composer install |
|
composer.json.txt with these file I can reproduce nested duplications:
|
|
Comparison of modman file:
|
|
I updated modman file and re-installed module from my repo: Installation works fine, no nested duplication. Question is now: Is this a magento-composer-installer bug or wrong usage of modman mapping syntax |
|
Kudos, SonarCloud Quality Gate passed! |








Avoid nested duplication if a module folder exists when using copy strategy.