Task #67363

Support Composer classloader from vendor directory

Added by Mathias Brodala over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Category:
Miscellaneous
Target version:
Start date:
2015-06-09
Due date:
% Done:

50%

TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

If the typo3/cms package is kept in the Composer vendor-dir, e.g. by disabling the typo3/cms-composer-installers package, the Composer autoload.php is not detected.

This use case should be supported, since this is a rather usual setup in Composer-based environments where typo3/cms is not supposed to take over the project root directory.


Related issues

Duplicates TYPO3 Core - Bug #66994: Composer autoload path detection is a bit too restricture Closed 2015-05-16

History

#1 Updated by Gerrit Code Review over 4 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40121

#2 Updated by Helmut Hummel over 4 years ago

Mathias Brodala wrote:

disabling the typo3/cms-composer-installers package, the Composer autoload.php is not detected.

this is not supported and there are no plans to support that.

What is planned is to actually read the vendor dir from the root composer.json file and include that autoload.php file accordingly.
But this is not easy to achieve as this needs to happen very early in the bootstrap.

See also #66994

#3 Updated by Helmut Hummel over 4 years ago

  • Status changed from Under Review to Closed

closing as duplicate

#4 Updated by Helmut Hummel about 4 years ago

Mathias Brodala wrote:

disabling the typo3/cms-composer-installers package

Just to be clear about that one. typo3/cms-composer-installers is a requirement of the typo3/cms package. If you disable this requirement, you are completely on your own. We can not and will never support such cases.

Also available in: Atom PDF