Issue Bug Closed

#57604PackageManager is unable to resolve composer PSR-4 namespaces

Jacob Rasmussen 04/03/14, 16:16 updated 06/23/15, 14:56

Description

Currently the package manager is only able to resolve PSR-0 namespaces.

This makes it impossible to include composer packages which rely on PSR-4 namespaces, such as Pelago\Emogrifier, unless the composer autoloader is included manually in a TYPO3 extension.

Steps to reproduce

Create a composer.json in the root of site path like this:

{
  "config": {
    "vendor-dir": "Packages/Libraries"
  },
  "minimum-stability": "dev"
  "require": {
    "pelago/emogrifier": "*"
  }
}

Run “composer install” in the path in order to fetch the package

Ensure typo3conf/PackageStates.php is updated – this can be done by uninstalling and installing a TYPO3 extension.

Activate the package manually by editing PackageStates.php, as it currently isn’t possible to activate composer packages through the UI or CLI

Try to instantiate the \Pelago\Emogrifier class which will fail

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.