Bug #55755
closed
Epic #47018: Implement Composer support and clean package manager API
Legacy packages with dependencies to other composer packages coudn't be installed
0%
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.
Updated by Gerrit Code Review almost 11 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 https://review.typo3.org/27404
Updated by Gerrit Code Review almost 11 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/27404
Updated by
Updated by Jacob Rasmussen over 10 years ago
It would be nice to get composer packages loaded - either through the suggested patch or by using the composer autoloader
Updated by Nicole Cordes over 9 years ago
- Target version changed from 6.2.0 to 7.3 (Packages)
- Sprint Focus set to On Location Sprint
Updated by Benni Mack over 9 years ago
- Status changed from Under Review to Rejected
fixed differently now. but for 6.2 this won't go in. sorry guys. if you have any feedback, feel free to send me an email.
Updated by Anja Leichsenring almost 9 years ago
- Sprint Focus deleted (
On Location Sprint)