Issue Bug Rejected

#55755Legacy packages with dependencies to other composer packages coudn't be installed

Helge Funk 02/07/14, 10:51 updated 01/08/16, 11:17

Description

It’s not possible to install a composer ready legacy package with dependencies to other composer packages stored in the „Packages“ folder. The Packages will be scanned and added to the PackageStates.php, but the state remains on „inactive“.
There is no possibility to activate those packages like in Flow.

Steps to reproduce: Try to install a composer ready extension with dependencies to other not TYPO3 related packages

A workaround for now is to assume that composer packages are activated by default.

Reviews 1