tmaroschik
commented
9 years ago Hey Uwe,
we thought about during development, but were against it. The reason is, that activating an extension in TYPO3 changes data of your installation, not just code. Further this plugin won't know if TYPO3 is really installed and database tables set up. Activating extensions and processing database migrations is rather the duty of TYPO3 itself or your deployment infrastructure (e.g. Surf).
You might achieve what you want with the "scripts" section defined in your root composer.json. See here for more information https://getcomposer.org/doc/articles/scripts.md
Cheers
Hi,
I'm completely new to composer and that's why unsure if it's the right place for it. Is it usefull when the TYPO3 composer plugin installs an extensions (and it's dependencies) using the CLI API and not just downloading them? I've tried to implement it and it works basically. But before I spend further time to improve the implementation I wanted to ask if it's the right way of doing this. I couldn't find any discussion about it so far.
Kind regards Uwe