Goes back to not extending Symfony's Application class or using the Command class. This is a bit of a re-design from before the Symfony inheritance change to not pull in some of the more complex app logic and address a couple design issues that made things like running multiple commands somewhat tricky, changes include:
No more CommandInterface, everything extends the concrete AbstractCommand class
AbstractCommand class has execute/doExecute methods (matching naming from Joomla's AbstractApplication), these parallel the Symfony Command class' run and execute methods as far as functionality goes
Input and Output are injected into commands now versus pulled from the application
AbstractCommand now uses configure as the constructor's configuration hook, same name as Symfony's class (replaces old initialise method)
AbstractCommand supports setting command names in a static property (similar to Symfony)
Summary of Changes
Goes back to not extending Symfony's
Applicationclass or using theCommandclass. This is a bit of a re-design from before the Symfony inheritance change to not pull in some of the more complex app logic and address a couple design issues that made things like running multiple commands somewhat tricky, changes include:CommandInterface, everything extends the concreteAbstractCommandclassAbstractCommandclass hasexecute/doExecutemethods (matching naming from Joomla'sAbstractApplication), these parallel the SymfonyCommandclass'runandexecutemethods as far as functionality goesAbstractCommandnow usesconfigureas the constructor's configuration hook, same name as Symfony's class (replaces oldinitialisemethod)AbstractCommandsupports setting command names in a static property (similar to Symfony)