The autoload section in the Magento2 project composer.json

[moleman]

Hi,

Is there any special reason why the autoloading mapping of both *Magento\Framework* and *Magento\Setup* are in the Magento2 project composer.json file? Wouldn't it be better to have them in the packages where they belong, *Magento\Framework* in magento/framework and *Magento\Setup* in magento/magento2-base?

The reason why is that it would make the Magento2 project composer.json cleaner and you wouldn't have to specify it in your own project composer.json when you require the "magento/product-community-edition" package.

[buskamuza]

Hi @moleman ,

magento/framework and magento/magento2-base, actually, have their autoload.
The reason why this Git repository (magento/magento2) is that it includes whole Magento and so does not download components (such as Framework) via Composer. That's why composer.json of the Git repository includes duplicated information to let Composer read and process it.

UPD: looks like, you're right about Setup - it's declared in the project instead of the base component. Though for the Framework autoload is included in the framework package.

[mazhalai]

@moleman this is due to dependency on magento-composer-installer which copies the components to the folder instead of loading directly from vendor. Some of this is work in progress. See related issue in PR #1490

[moleman]

@buskamuza @mazhalai Aha, the Framework package autoload has "Magento\Framework": "" which is correct mapping in the package context but the project needs to map "Magento\Framework" to "lib/internal/Magento/Framework/" because thats the location where the package files will be placed in the project by the installer. Then I understand. Thanks.

But still, I think that the autoloading of the setup can be moved to the magento/magento2-base composer.json because the folder structure is the same in the package as in the project.

[piotrekkaminski]

@buskamuza are there any changes here?

[buskamuza]

@moleman , yes, it would be better to move the autoload to corresponding packages. I created an internal ticket for this MAGETWO-70242

[magento-engcom-team]

@moleman, thank you for your report.
We've created internal ticket(s) MAGETWO-70242 to track progress on the issue.