Epic #85990: Extbase CommandControllers vs. Symfony/Console Integration
Migrate EM CommandController to symfony/command
The Extension Manager CLI commands are the only commands from TYPO3 Core that are registered and implemented differently than all others.
If we really want to unify the CLI part, we need to get to one common basis to continue from (see https://decisions.typo3.org/t/command-line-unification/438/2) and this is one important step towards that goal.
[TASK] Migrate extension commands to Symfony
The Extbase command controller from Extension Manager is the only
CommandController used in TYPO3 Core (apart from extbase:help), all
others have been migrated to symfony/console commands.
This however is now only possible due to the recent migration to define
these commands as "non-schedulable" so they do not show up in the
scheduler as a possible command to be called repeatedly.
For the "extensionmanager:extension:dumpclassloadinginformation"
call, the functionality is moved to EXT:core as this is not related to any
functionality in ExtensionManager, as it does not need any information
of this. This command has been made available under "dumpautoload"
to get closer on the naming scheme of native composer.
"install" and "uninstall" however rely on the DI concept of Extbase and
Extensionmanager to inject necessary components and is tightly
intertwined. These are now provided as "extension:activate" and
"extension:deactivate" respectively to convey their purpose and especially
show that the latter does not remove any data or code.
Tested-by: TYPO3com <firstname.lastname@example.org>
Reviewed-by: Nicole Cordes <email@example.com>
Reviewed-by: Mathias Brodala <firstname.lastname@example.org>
Tested-by: Mathias Brodala <email@example.com>
Reviewed-by: Wouter Wolters <firstname.lastname@example.org>
Reviewed-by: Georg Ringer <email@example.com>
Tested-by: Georg Ringer <firstname.lastname@example.org>